From: Jonathan Cameron <jic23@kernel.org>
To: "Barnabás Czémán" <barnabas.czeman@mainlining.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Albrieux <jonathan.albrieux@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux@mainlining.org
Subject: Re: [PATCH v2 1/3] iio: magnetometer: ak8975: Fix reading for ak099xx sensors
Date: Sat, 10 Aug 2024 11:27:12 +0100 [thread overview]
Message-ID: <20240810112712.191d6576@jic23-huawei> (raw)
In-Reply-To: <45915CD6-A9BB-4071-ABCC-8DE76F7066C3@mainlining.org>
On Tue, 06 Aug 2024 19:54:56 +0200
Barnabás Czémán <barnabas.czeman@mainlining.org> wrote:
> On August 6, 2024 6:19:25 PM GMT+02:00, Jonathan Cameron <jic23@kernel.org> wrote:
> >On Tue, 06 Aug 2024 08:10:18 +0200
> >Barnabás Czémán <barnabas.czeman@mainlining.org> wrote:
> >
> >Hi Barnabás,
> >
> >Welcome to IIO.
> >
> >> ST2 register read should be placed after read measurment data,
> >> because it will get correct values after it.
> >
> >What is the user visible result of this? Do we detect errors when none
> >are there? Do we have a datasheet reference for the status being
> >update on the read command, not after the trigger?
>
> Second read will fail. In the datasheet ST2 comes after measurment data read. Here is some explanation from datasheet.
>
> "When ST2 register is read, AK09918 judges that data reading is finished. Stored measurement data is
> protected during data reading and data is not updated. By reading ST2 register, this protection is
> released. It is required to read ST2 register after data reading."
>
Thanks. Please add more of that detail to the patch description for v3.
> So if ST2 is read before measurment it will stuck at protected mode.
> >>
> >Needs a Fixes tag to let us know how far to backport the fix.
> I think it is broken since 09912 was added but i cannot verify i have only devices with 09918.
> >
I wasn't meaning devices, but rather what patch broke the kernel code.
It might be the original driver introduction.
If we can add a Fixes tag that makes it much easier for stable + distributions
to work out whether to pick the fix up or not.
next prev parent reply other threads:[~2024-08-10 10:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 6:10 [PATCH v2 0/3] Add support for AK09918 Barnabás Czémán
2024-08-06 6:10 ` [PATCH v2 1/3] iio: magnetometer: ak8975: Fix reading for ak099xx sensors Barnabás Czémán
2024-08-06 16:19 ` Jonathan Cameron
2024-08-06 17:54 ` Barnabás Czémán
2024-08-10 10:27 ` Jonathan Cameron [this message]
2024-08-07 15:15 ` barnabas.czeman
2024-08-06 6:10 ` [PATCH v2 2/3] dt-bindings: iio: imu: magnetometer: Add ak09118 Barnabás Czémán
2024-08-06 16:00 ` Conor Dooley
2024-08-06 16:01 ` Conor Dooley
2024-08-07 6:03 ` Krzysztof Kozlowski
2024-08-06 6:10 ` [PATCH v2 3/3] iio: magnetometer: ak8975: Add AK09118 support Barnabás Czémán
2024-08-06 16:26 ` Jonathan Cameron
2024-08-07 6:04 ` Krzysztof Kozlowski
2024-08-12 14:26 ` Barnabás Czémán
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=20240810112712.191d6576@jic23-huawei \
--to=jic23@kernel.org \
--cc=barnabas.czeman@mainlining.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathan.albrieux@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@mainlining.org \
--cc=robh@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