mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-11-18 01:34:14 +08:00
iio: adc: max9611: Fix too short conversion time delay
[ Upstream commit9fd229c478
] As of commitb9ddd50911
("iio: adc: max9611: Fix temperature reading in probe"), max9611 initialization sometimes fails on the Salvator-X(S) development board with: max9611 4-007f: Invalid value received from ADC 0x8000: aborting max9611: probe of 4-007f failed with error -5 The max9611 driver tests communications with the chip by reading the die temperature during the probe function, which returns an invalid value. According to the datasheet, the typical ADC conversion time is 2 ms, but no minimum or maximum values are provided. Maxim Technical Support confirmed this was tested with temperature Ta=25 degreeC, and promised to inform me if a maximum/minimum value is available (they didn't get back to me, so I assume it is not). However, the driver assumes a 1 ms conversion time. Usually the usleep_range() call returns after more than 1.8 ms, hence it succeeds. When it returns earlier, the data register may be read too early, and the previous measurement value will be returned. After boot, this is the temperature POR (power-on reset) value, causing the failure above. Fix this by increasing the delay from 1000-2000 µs to 3000-3300 µs. Note that this issue has always been present, but it was exposed by the aformentioned commit. Fixes:69780a3bbc
("iio: adc: Add Maxim max9611 ADC driver") Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> Reviewed-by: Jacopo Mondi <jacopo+renesas@jmondi.org> Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:
parent
f7a667db91
commit
8db2bb9681
@ -89,6 +89,12 @@
|
||||
#define MAX9611_TEMP_SCALE_NUM 1000000
|
||||
#define MAX9611_TEMP_SCALE_DIV 2083
|
||||
|
||||
/*
|
||||
* Conversion time is 2 ms (typically) at Ta=25 degreeC
|
||||
* No maximum value is known, so play it safe.
|
||||
*/
|
||||
#define MAX9611_CONV_TIME_US_RANGE 3000, 3300
|
||||
|
||||
struct max9611_dev {
|
||||
struct device *dev;
|
||||
struct i2c_client *i2c_client;
|
||||
@ -236,11 +242,9 @@ static int max9611_read_single(struct max9611_dev *max9611,
|
||||
return ret;
|
||||
}
|
||||
|
||||
/*
|
||||
* need a delay here to make register configuration
|
||||
* stabilize. 1 msec at least, from empirical testing.
|
||||
*/
|
||||
usleep_range(1000, 2000);
|
||||
/* need a delay here to make register configuration stabilize. */
|
||||
|
||||
usleep_range(MAX9611_CONV_TIME_US_RANGE);
|
||||
|
||||
ret = i2c_smbus_read_word_swapped(max9611->i2c_client, reg_addr);
|
||||
if (ret < 0) {
|
||||
@ -507,7 +511,7 @@ static int max9611_init(struct max9611_dev *max9611)
|
||||
MAX9611_REG_CTRL2, 0);
|
||||
return ret;
|
||||
}
|
||||
usleep_range(1000, 2000);
|
||||
usleep_range(MAX9611_CONV_TIME_US_RANGE);
|
||||
|
||||
return 0;
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user