From: "Nuno Sá" <noname.nuno@gmail.com>
To: Matti Vaittinen <mazziesaccount@gmail.com>,
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: accel: kx022a: Improve reset delay
Date: Thu, 14 Nov 2024 10:43:05 +0100 [thread overview]
Message-ID: <be375e24f74997743743fadf68125e176c23e2df.camel@gmail.com> (raw)
In-Reply-To: <ZzWfXbjaDkFnu_Jg@mva-rohm>
On Thu, 2024-11-14 at 08:57 +0200, Matti Vaittinen wrote:
> All the sensors supported by kx022a driver seemed to require some delay
> after software reset to be operational again. More or less a random
> msleep(1) was added to cause the driver to go to sleep so the sensor has
> time to become operational again.
>
> Now we have official docuumentation available:
> https://fscdn.rohm.com/kionix/en/document/AN010_KX022ACR-Z_Power-on_Procedure_E.pdf
> https://fscdn.rohm.com/kionix/en/document/TN027-Power-On-Procedure.pdf
> https://fscdn.rohm.com/kionix/en/document/AN011_KX134ACR-LBZ_Power-on_Procedure_E.pdf
>
> stating the required time is 2 ms.
>
> Due to the nature of the current msleep implementation, the msleep(1) is
> likely to be sleeping more than 2ms already - but the value "1" is
> misleading in case someone needs to optimize the start time and change
> the msleep to a more accurate delay. Hence it is better for
> "documentation" purposes to use value which actually reflects the
> specified 2ms wait time.
>
> Change the value of delay after software reset to match the
> specifications and add links to the power-on procedure specifications.
>
> Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
> ---
> Sorry for not including this to the KX134ACR-LBZ series I sent
> yesterday. It was only half an hour after I had sent the KX134ACR-LBZ
> support when I was notified about the existence of the KX022ACR-Z
> start-up procedure specification... Hence this lone patch to code which
> I just sent a miscallaneous series for before.
>
> drivers/iio/accel/kionix-kx022a.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iio/accel/kionix-kx022a.c b/drivers/iio/accel/kionix-
> kx022a.c
> index 32387819995d..ccabe2e3b130 100644
> --- a/drivers/iio/accel/kionix-kx022a.c
> +++ b/drivers/iio/accel/kionix-kx022a.c
> @@ -1121,10 +1121,15 @@ static int kx022a_chip_init(struct kx022a_data *data)
> return ret;
>
> /*
> - * I've seen I2C read failures if we poll too fast after the sensor
> - * reset. Slight delay gives I2C block the time to recover.
> + * According to the power-on procedure documents, there is (at least)
> + * 2ms delay required after the software reset. This should be same
> for
> + * all, KX022ACR-Z, KX132-1211, KX132ACR-LBZ and KX134ACR-LBZ.
> + *
> + *
> https://fscdn.rohm.com/kionix/en/document/AN010_KX022ACR-Z_Power-on_Procedure_E.pdf
> + *
> https://fscdn.rohm.com/kionix/en/document/TN027-Power-On-Procedure.pdf
> + *
> https://fscdn.rohm.com/kionix/en/document/AN011_KX134ACR-LBZ_Power-on_Procedure_E.pdf
> */
> - msleep(1);
> + msleep(2);
msleep() is not advisable for something lower than 20ms. Maybe take the
opportunity and change it to fsleep()?
- Nuno Sá
next prev parent reply other threads:[~2024-11-14 9:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 6:57 [PATCH] iio: accel: kx022a: Improve reset delay Matti Vaittinen
2024-11-14 9:43 ` Nuno Sá [this message]
2024-11-14 9:54 ` Matti Vaittinen
2024-11-14 10:46 ` Nuno Sá
2024-11-14 11:30 ` Matti Vaittinen
2024-11-14 12:26 ` Nuno Sá
2024-11-15 6:20 ` Matti Vaittinen
2024-11-15 7:44 ` Nuno Sá
2024-11-19 5:55 ` Matti Vaittinen
2024-11-19 9:01 ` Nuno Sá
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=be375e24f74997743743fadf68125e176c23e2df.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.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