From: Jonathan Cameron <jic23@kernel.org>
To: Lakshmi Yadlapati <lakshmiy@us.ibm.com>
Cc: eajames@linux.ibm.com, lars@metafoo.de, joel@jms.id.au,
andrew@aj.id.au, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] iio: pressure: dps310: Adjust Timeout Settings
Date: Sun, 3 Sep 2023 12:53:09 +0100 [thread overview]
Message-ID: <20230903125309.12c59189@jic23-huawei> (raw)
In-Reply-To: <20230829180222.3431926-2-lakshmiy@us.ibm.com>
On Tue, 29 Aug 2023 13:02:22 -0500
Lakshmi Yadlapati <lakshmiy@us.ibm.com> wrote:
> The DPS310 sensor chip has been encountering intermittent errors while
> reading the sensor device across various system designs. This issue causes
> the chip to become "stuck," preventing the indication of "ready" status
> for pressure and temperature measurements in the MEAS_CFG register.
>
> To address this issue, this commit fixes the timeout settings to improve
> sensor stability:
> - After sending a reset command to the chip, the timeout has been extended
> from 2.5 ms to 15 ms, aligning with the DPS310 specification.
> - The read timeout value of the MEAS_CFG register has been adjusted from
> 20ms to 30ms to match the specification.
>
> Signed-off-by: Lakshmi Yadlapati <lakshmiy@us.ibm.com>
Hi Lakshmi,
This seems reasonable to me, but as we probably want to backport it to
stable kernels, please could you figure out an appropriate Fixes tag.
Fine to just reply to this email with the tag rather than resend.
Thanks
Jonathan
> ---
> drivers/iio/pressure/dps310.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/iio/pressure/dps310.c b/drivers/iio/pressure/dps310.c
> index b10dbf5cf494..1ff091b2f764 100644
> --- a/drivers/iio/pressure/dps310.c
> +++ b/drivers/iio/pressure/dps310.c
> @@ -57,8 +57,8 @@
> #define DPS310_RESET_MAGIC 0x09
> #define DPS310_COEF_BASE 0x10
>
> -/* Make sure sleep time is <= 20ms for usleep_range */
> -#define DPS310_POLL_SLEEP_US(t) min(20000, (t) / 8)
> +/* Make sure sleep time is <= 30ms for usleep_range */
> +#define DPS310_POLL_SLEEP_US(t) min(30000, (t) / 8)
> /* Silently handle error in rate value here */
> #define DPS310_POLL_TIMEOUT_US(rc) ((rc) <= 0 ? 1000000 : 1000000 / (rc))
>
> @@ -402,8 +402,8 @@ static int dps310_reset_wait(struct dps310_data *data)
> if (rc)
> return rc;
>
> - /* Wait for device chip access: 2.5ms in specification */
> - usleep_range(2500, 12000);
> + /* Wait for device chip access: 15ms in specification */
> + usleep_range(15000, 55000);
> return 0;
> }
>
next prev parent reply other threads:[~2023-09-03 11:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 18:02 [PATCH v1 0/1] iio: pressure: dps310: Adjust Timeout Settings Lakshmi Yadlapati
2023-08-29 18:02 ` [PATCH v1 1/1] " Lakshmi Yadlapati
2023-09-03 11:53 ` Jonathan Cameron [this message]
2023-09-06 14:55 ` Lakshmi Yadlapati
2023-09-10 13:50 ` Jonathan Cameron
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=20230903125309.12c59189@jic23-huawei \
--to=jic23@kernel.org \
--cc=andrew@aj.id.au \
--cc=eajames@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=lakshmiy@us.ibm.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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