iio: accel: mma8452: remove the reset operation during driver probe
PATCH 1/1 iio: accel: mma8452: remove the reset operation during driver probe
From: Haibo Chen <[email protected]>
Though Sensor Datasheet define this reset bit in it's CTRL_REG2 register, but seems the actual hardware behavior do not align with the doc expect. Once the reset bit is set, sensor can’t give back an I2C ack, which will cause the probe fail. So just remove this reset operation.
--- drivers/iio/accel/mma8452.c | 28 ---------------------------- 1 file changed, 28 deletions(-)
drivers/iio/accel/mma8452.c +0 -28
@@ -1481,30 +1481,6 @@ static void mma8452_trigger_cleanup(struct iio_dev *indio_dev)iio_trigger_unregister (indio_dev->trig); } -static int mma8452_reset (struct i2c_client *client) -{ -int i; -int ret; - - ret =i2c_smbus_write_byte_data (client,MMA8452_CTRL_REG2 , -MMA8452_CTRL_REG2_RST ); -if (ret <0 ) -return ret; - -for (i =0 ; i <10 ; i++) { -usleep_range (100 ,200 ); - ret =i2c_smbus_read_byte_data (client,MMA8452_CTRL_REG2 ); -if (ret == -EIO ) -continue ;/* I2C comm reset */ -if (ret <0 ) -return ret; -if (!(ret &MMA8452_CTRL_REG2_RST )) -return 0 ; - } - -return -ETIMEDOUT ; -} -static const struct of_device_id mma8452_dt_ids[] = { { .compatible ="fsl,mma8451" , .data = &mma_chip_info_table[mma8451] }, { .compatible ="fsl,mma8452" , .data = &mma_chip_info_table[mma8452] },
@@ -1591,10 +1567,6 @@ static int mma8452_probe(struct i2c_client *client, indio_dev->num_channels = data->chip_info->num_channels; indio_dev->available_scan_masks = mma8452_scan_masks; - ret =mma8452_reset (client); -if (ret <0 ) - goto disable_regulators; - data->data_cfg =MMA8452_DATA_CFG_FS_2G ; ret =i2c_smbus_write_byte_data (client,MMA8452_DATA_CFG , data->data_cfg);
Signature · 1 line
2.25.1
Quoted 9 lines · On Tue, 22 Feb 2022 12:45:51 +0800 <[email protected]> wrote:
From: Haibo Chen <[email protected]>
Though Sensor Datasheet define this reset bit in it's
CTRL_REG2register, but seems the actual hardware behavior do not align with the doc expect. Once the reset bit is set, sensor can’t give back an I2C ack, which will cause the probe fail. So just remove this reset operation.Signed-off-by Haibo Chen <[email protected]>
Hi Haibo,
I'm not really that keen to remove reset on probe as it's normally a good way to ensure we get a device into a sane state as we have no idea what has run before we load the driver.
Wolfram is there a standard way to work around missing ACK in cases like this? Would just ignoring the return value be fine or are their i2c masters that will get stuck if they don't get the expected ack?
Jonathan
Quoted 50 lines
--- drivers/iio/accel/mma8452.c | 28 ---------------------------- 1 file changed, 28 deletions(-)drivers/iio/accel/mma8452.c +0
-28@@ -1481,30 +1481,6 @@ static void mma8452_trigger_cleanup(struct iio_dev *indio_dev)iio_trigger_unregister (indio_dev->trig); } -static int mma8452_reset (struct i2c_client *client) -{ -int i; -int ret; - - ret =i2c_smbus_write_byte_data (client,MMA8452_CTRL_REG2 , -MMA8452_CTRL_REG2_RST ); -if (ret <0 ) -return ret; - -for (i =0 ; i <10 ; i++) { -usleep_range (100 ,200 ); - ret =i2c_smbus_read_byte_data (client,MMA8452_CTRL_REG2 ); -if (ret == -EIO ) -continue ;/* I2C comm reset */ -if (ret <0 ) -return ret; -if (!(ret &MMA8452_CTRL_REG2_RST )) -return 0 ; - } - -return -ETIMEDOUT ; -} -static const struct of_device_id mma8452_dt_ids[] = { { .compatible ="fsl,mma8451" , .data = &mma_chip_info_table[mma8451] }, { .compatible ="fsl,mma8452" , .data = &mma_chip_info_table[mma8452] },@@ -1591,10 +1567,6 @@ static int mma8452_probe(struct i2c_client *client, indio_dev->num_channels = data->chip_info->num_channels; indio_dev->available_scan_masks = mma8452_scan_masks; - ret =mma8452_reset (client); -if (ret <0 ) - goto disable_regulators; - data->data_cfg =MMA8452_DATA_CFG_FS_2G ; ret =i2c_smbus_write_byte_data (client,MMA8452_DATA_CFG , data->data_cfg);
Quoted 25 lines
-----Original Message-----
From: Jonathan Cameron [mailto:[email protected]]
Sent: 2022年2月23日 0:44
To: Bough Chen <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; [email protected]; dl-linux-imx <[email protected]>; Wolfram Sang <[email protected]>
Subject: Re: [PATCH] iio: accel: mma8452: remove the reset operation during driver probeQuoted 9 lines · On Tue, 22 Feb 2022 12:45:51 +0800 <[email protected]> wrote:
From: Haibo Chen <[email protected]>
Though Sensor Datasheet define this reset bit in it's
CTRL_REG2register, but seems the actual hardware behavior do not align with the doc expect. Once the reset bit is set, sensor can’t give back an I2C ack, which will cause the probe fail. So just remove this reset operation.Signed-off-by Haibo Chen <[email protected]>Hi Haibo,
Quoted 7 lines
I'm not really that keen to remove reset on probe as it's normally a good way to ensure we get a device into a sane state as we have no idea what has run before we load the driver.
Wolfram is there a standard way to work around missing ACK in cases like this? Would just ignoring the return value be fine or are their i2c masters that will get stuck if they don't get the expected ack?
Currently, i2c masters will not get stuck. Only the sensor driver probe failed.
Let me do more test about this, currently I find this issue on fxls8471/mma8452, and this driver cover many sensors Not sure whether other sensors has the same behavior.
Best Regards
Haibo chen
Quoted 56 lines
Jonathan
drivers/iio/accel/mma8452.c static void mma8452_trigger_cleanup(struct
Quoted 9 lines
--- drivers/iio/accel/mma8452.c | 28 ---------------------------- 1 file changed, 28 deletions(-)drivers/iio/accel/mma8452.c +0
-0@@ -1481,30 +1481,6 @@ static void mma8452_trigger_cleanup(struct
iio_dev*indio_dev)Quoted 18 lines
drivers/iio/accel/mma8452.c +0
-15iio_trigger_unregister (indio_dev->trig); } -static int mma8452_reset(struct i2c_client *client) -{ -int i; -int ret; - - ret =i2c_smbus_write_byte_data (client,MMA8452_CTRL_REG2 , -MMA8452_CTRL_REG2_RST ); -if (ret <0 ) -return ret; - -for (i =0 ; i <10 ; i++) { -usleep_range (100 ,200 ); - ret =i2c_smbus_read_byte_data (client,MMA8452_CTRL_REG2 ); -if (ret == -EIO ) -continue ;/* I2C comm reset */ -if (ret <0 )drivers/iio/accel/mma8452.c static void mma8452_trigger_cleanup(struct iio_dev *indio_dev)
Quoted 10 lines
drivers/iio/accel/mma8452.c +0
-8-return ret; -if (!(ret &MMA8452_CTRL_REG2_RST )) -return 0 ; - } - -return -ETIMEDOUT ; -} -static const struct of_device_id mma8452_dt_ids[] = { { .compatible = "fsl,mma8451", .data =&mma_chip_info_table[mma8451] },
drivers/iio/accel/mma8452.c static void mma8452_trigger_cleanup(struct · line 1486
Quoted 1 line
drivers/iio/accel/mma8452.c +0
-0{ .compatible = "fsl,mma8452", .data =&mma_chip_info_table[mma8452]
Quoted 1 line
}, @@ -1591,10 +1567,6 @@ static int mma8452_probe(struct
i2c_client*client,
Quoted 10 lines
drivers/iio/accel/mma8452.c +0
-4indio_dev->num_channels = data->chip_info->num_channels; indio_dev->available_scan_masks = mma8452_scan_masks; - ret =mma8452_reset (client); -if (ret <0 ) - goto disable_regulators; - data->data_cfg =MMA8452_DATA_CFG_FS_2G ; ret =i2c_smbus_write_byte_data (client,MMA8452_DATA_CFG , data->data_cfg);
Quoted 4 lines
Quoted 4 lines
Wolfram is there a standard way to work around missing ACK in cases like this? Would just ignoring the return value be fine or are their i2c masters that will get stuck if they don't get the expected ack?
Did I get this right: the reset procedures terminates the ACK and STOP? And the client expects a new START condition for communication?
Jonathan Cameron
maintainerQuoted 7 lines · On Thu, 24 Feb 2022 18:33:26 +0100 Wolfram Sang <[email protected]> wrote:
Quoted 3 lines
Quoted 3 lines
Wolfram is there a standard way to work around missing ACK in cases like this? Would just ignoring the return value be fine or are their i2c masters that will get stuck if they don't get the expected ack?
Did I get this right: the reset procedures terminates the ACK and STOP? And the client expects a new START condition for communication?
@Bough Chen,
I'm assuming this is still an issue for you? If so can you reply to Wolfram so we can hopefully move this forwards.
Found this because it's still listed as needing an action in the IIO patchwork.
Thanks,
Jonathan
Quoted 22 lines
-----Original Message-----
From: Jonathan Cameron <[email protected]>
Sent: 2022年6月5日 0:17
To: Wolfram Sang <[email protected]>
Cc: Bough Chen <[email protected]>; Jonathan Cameron <[email protected]>; [email protected]; [email protected]; [email protected]; dl-linux-imx <[email protected]>
Subject: Re: [PATCH] iio: accel: mma8452: remove the reset operation during driver probeQuoted 7 lines · On Thu, 24 Feb 2022 18:33:26 +0100 Wolfram Sang <[email protected]> wrote:
Quoted 3 lines
Quoted 3 lines
Wolfram is there a standard way to work around missing ACK in cases like this? Would just ignoring the return value be fine or are their i2c masters that will get stuck if they don't get the expected ack?
Did I get this right: the reset procedures terminates the ACK and STOP? And the client expects a new START condition for communication?
Quoted 6 lines
@Bough Chen,
I'm assuming this is still an issue for you? If so can you reply to Wolfram so we can hopefully move this forwards.
Found this because it's still listed as needing an action in the IIO patchwork.
Hi Jonathan,
Give me few days to switch my current work to this patch work.
Thanks
Bough Chen
Quoted 4 lines
Thanks,
Jonathan
Quoted 11 lines
-----Original Message-----
From: Jonathan Cameron <[email protected]>
Sent: 2022年6月5日 0:17
To: Wolfram Sang <[email protected]>
Cc: Bough Chen <[email protected]>; Jonathan Cameron <[email protected]>; [email protected]; [email protected]; [email protected]; dl-linux-imx <[email protected]>
Subject: Re: [PATCH] iio: accel: mma8452: remove the reset operation during driver probe
Quoted 11 lines
Quoted 7 lines · On Thu, 24 Feb 2022 18:33:26 +0100 Wolfram Sang <[email protected]> wrote:
Quoted 3 lines
Quoted 3 lines
Wolfram is there a standard way to work around missing ACK in cases like this? Would just ignoring the return value be fine or are their i2c masters that will get stuck if they don't get the expected ack?
Did I get this right: the reset procedures terminates the ACK and STOP? And the client expects a new START condition for communication?
Hi
I use a I2C logic analyzer and find this reset just terminate ACK, and I2C bus controller then detect this NACK, and give a STOP. After that, I2C bus work normal. If just ignore this return, everything continue will be fine.
Seems for this sensor, after the reset bit is set, it works immediately, so will not give ACK.
I will send a v2 patch, just ignore this return rather than remove the whole reset operation.
Best Regards
Bough Chen
Quoted 10 lines
@Bough Chen,
I'm assuming this is still an issue for you? If so can you reply to Wolfram so we can hopefully move this forwards.
Found this because it's still listed as needing an action in the IIO patchwork.
Thanks,
Jonathan