From: Jacopo Mondi <jacopo@jmondi.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>,
Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-iio@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adc: max9611: Fix too short conversion time delay
Date: Wed, 13 Nov 2019 10:38:28 +0100 [thread overview]
Message-ID: <20191113093828.vk5qqtlr7bs5z5fb@uno.localdomain> (raw)
In-Reply-To: <20191113092133.23723-1-geert+renesas@glider.be>
[-- Attachment #1: Type: text/plain, Size: 3048 bytes --]
Hi Geert,
On Wed, Nov 13, 2019 at 10:21:33AM +0100, Geert Uytterhoeven wrote:
> As of commit b9ddd5091160793e ("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. 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 2000-2200 µs.
>
> Note that this issue has always been present, but it was exposed by the
> aformentioned commit.
>
> Fixes: 69780a3bbc0b1e7e ("iio: adc: Add Maxim max9611 ADC driver")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> This problem was exposed in v5.3.
>
> After this patch, probing of the two max9611 sensors succeeded during
> ca. 3000 boot cycles on Salvator-X(S) boards, equipped with various
> R-Car H3/M3-W/M3-N SoCs.
> ---
> drivers/iio/adc/max9611.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iio/adc/max9611.c b/drivers/iio/adc/max9611.c
> index da073d72f649f829..b0755f25356d700d 100644
> --- a/drivers/iio/adc/max9611.c
> +++ b/drivers/iio/adc/max9611.c
> @@ -89,6 +89,11 @@
> #define MAX9611_TEMP_SCALE_NUM 1000000
> #define MAX9611_TEMP_SCALE_DIV 2083
>
> +/*
> + * Conversion time is 2 ms (typically)
> + */
> +#define MAX9611_CONV_TIME_US_RANGE 2000, 2200
> +
Is a 20% sleep range enough or should it be slightly lengthen ?
Apart from this, thanks a lot for finding the issue root cause!
Reviewed-by: Jacopo Mondi <jacopo+renesas@jmondi.org>
Thanks
j
> struct max9611_dev {
> struct device *dev;
> struct i2c_client *i2c_client;
> @@ -238,9 +243,9 @@ static int max9611_read_single(struct max9611_dev *max9611,
>
> /*
> * need a delay here to make register configuration
> - * stabilize. 1 msec at least, from empirical testing.
> + * stabilize.
> */
> - usleep_range(1000, 2000);
> + usleep_range(MAX9611_CONV_TIME_US_RANGE);
>
> ret = i2c_smbus_read_word_swapped(max9611->i2c_client, reg_addr);
> if (ret < 0) {
> @@ -507,7 +512,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;
> }
> --
> 2.17.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-11-13 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 9:21 [PATCH] iio: adc: max9611: Fix too short conversion time delay Geert Uytterhoeven
2019-11-13 9:38 ` Jacopo Mondi [this message]
2019-11-13 9:46 ` Geert Uytterhoeven
2019-11-13 9:58 ` Jacopo Mondi
2019-11-13 18:00 ` Wolfram Sang
2019-11-13 18:32 ` Geert Uytterhoeven
2019-11-14 9:08 ` Wolfram Sang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191113093828.vk5qqtlr7bs5z5fb@uno.localdomain \
--to=jacopo@jmondi.org \
--cc=geert+renesas@glider.be \
--cc=jacopo+renesas@jmondi.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=wsa+renesas@sang-engineering.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).