From: Kaustabh Chakraborty <kauschluss@disroot.org>
To: Conor Dooley <conor@kernel.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
linux-iio@vger.kernel.org, denis.ciocca@st.com,
devicetree@vger.kernel.org, linus.walleij@linaro.org,
robh+dt@kernel.org, kauschluss@disroot.org
Subject: Re: [PATCH v4 2/2] dt-bindings: iio: st-sensors: add LIS2DS12 accelerometer
Date: Thu, 20 Jun 2024 16:42:39 +0000 [thread overview]
Message-ID: <c4c7532b6b2ba08e24043b432431303b@disroot.org> (raw)
In-Reply-To: <20240618-jockstrap-gains-de25ff6a969b@spud>
On 2024-06-18 17:38, Conor Dooley wrote:
> On Tue, Jun 18, 2024 at 12:21:17PM +0000, Kaustabh Chakraborty wrote:
>> On 2024-06-15 13:49, Jonathan Cameron wrote:
>> > On Sat, 15 Jun 2024 09:46:59 +0000
>> > Kaustabh Chakraborty <kauschluss@disroot.org> wrote:
>> >
>> >> On 2024-06-11 18:17, Conor Dooley wrote:
>> >> > On Tue, Jun 11, 2024 at 09:35:53PM +0530, Kaustabh Chakraborty wrote:
>> >> >> Add compatible for LIS2DS12 accelerometer by STMicroelectronics.
>> >> >
>> >> > I can see that! Your commit message should mention why this device
>> >> > is not compatible with existing variants.
>> >>
>> >> Sure, is adding the WhoAmI value enough? Or do I also have to
>> >> explain the different registers and sensor settings.
>> >>
>> > Who ami is not enough, but a statement along the lines of
>> > "The register interface is not compatible with existing parts, for
>> > example addresses and contents of numerous registers are different"
>> >
>> > With whatever the actual differences are.
>>
>> "LIS2DS12 is an accelerometer by STMicroelectronics. It is identifiable by
>> its WhoAmI value 0x43.
>>
>> Its register interface is not compatible with existing parts. For example:
>>
>> - The full-scale values are present in register 0x20, in bits 2 and 3
>> (mask 0x0c).
>>
>> - The full-scale values 2G, 4G, 8G, and 16G correspond to the register
>> values 0x00, 0x02, 0x03, 0x01 respectively.
>>
>> Add the compatible string without any fallback."
>>
>> Is this good enough?
>
> I don't know the other devices, so please highlight how the examples you
> give here are different to the existing ones please.
Are these acceptable?
- The full-scale values are present in register 0x20, in bits 2 and 3
(mask 0x0c).
Most other supported sensors have the register address set to 0x21,
0x23, 0x24, or 0x25.
There is one sensor setting though (bearing WhoAmI 0x3b) which has
it's address set to 0x20, but the mask is set to 0x20, not 0x0c.
- The full-scale values 2G, 4G, 8G, and 16G correspond to the register
values 0x00, 0x02, 0x03, 0x01 respectively.
None of the sensor settings have the value 0x01 associated with 16G.
next prev parent reply other threads:[~2024-06-20 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 16:05 [PATCH v4 1/2] iio: accel: st_accel: add support for LIS2DS12 Kaustabh Chakraborty
2024-06-11 16:05 ` [PATCH v4 2/2] dt-bindings: iio: st-sensors: add LIS2DS12 accelerometer Kaustabh Chakraborty
2024-06-11 18:17 ` Conor Dooley
2024-06-15 9:46 ` Kaustabh Chakraborty
2024-06-15 12:11 ` Conor Dooley
2024-06-15 17:56 ` Jonathan Cameron
2024-06-15 13:49 ` Jonathan Cameron
2024-06-18 12:21 ` Kaustabh Chakraborty
2024-06-18 17:38 ` Conor Dooley
2024-06-20 16:42 ` Kaustabh Chakraborty [this message]
2024-06-21 14:21 ` Conor Dooley
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=c4c7532b6b2ba08e24043b432431303b@disroot.org \
--to=kauschluss@disroot.org \
--cc=conor@kernel.org \
--cc=denis.ciocca@st.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).