From: Jonathan Cameron <jic23@kernel.org>
To: Darius Berghe <darius.berghe@analog.com>
Cc: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] dt-bindings: iio: adis16480: add devices to adis16480
Date: Fri, 1 Nov 2024 15:12:43 +0000 [thread overview]
Message-ID: <20241101151243.558a8577@jic23-huawei> (raw)
In-Reply-To: <20241101130742.3479110-3-darius.berghe@analog.com>
On Fri, 1 Nov 2024 15:07:42 +0200
Darius Berghe <darius.berghe@analog.com> wrote:
> Add the adis16486, adis16487 and adis16489 Six Degrees
> of Freedom Inertial Sensors to the list of compatible devices
> of the adis16480 iio subsystem driver.
Hi Darius
Please give a brief statement of what differs between these and the
many other compatibles in this binding (beyond the ID register)?
(usually scales, features etc)
In particularly you state in the docs patch that one of them
is functionally equivalent to an existing part so there a fallback
compatible is appropriate.
See how the st,lsm6dsx does it. The reason to do this it allows
the potential for an old kernel driver to work fine with a newer
device tree.
Other than that the series looks good to me.
Given we have a case where data could be shared, longer term
breaking up the chip_info array into individual structures would
allow sharing of the data.
The name handling in here isn't ideal as it relies on matching
in the spi_device_id table which is fragile. Doing that more
cleanly might break the sharing of structures. Oh well, not
relevant for this set anyway.
Jonathan
>
> Signed-off-by: Darius Berghe <darius.berghe@analog.com>
> ---
> Documentation/devicetree/bindings/iio/imu/adi,adis16480.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/imu/adi,adis16480.yaml b/Documentation/devicetree/bindings/iio/imu/adi,adis16480.yaml
> index e3eec38897bf..5bef2878a0df 100644
> --- a/Documentation/devicetree/bindings/iio/imu/adi,adis16480.yaml
> +++ b/Documentation/devicetree/bindings/iio/imu/adi,adis16480.yaml
> @@ -15,7 +15,10 @@ properties:
> - adi,adis16375
> - adi,adis16480
> - adi,adis16485
> + - adi,adis16486
> + - adi,adis16487
> - adi,adis16488
> + - adi,adis16489
> - adi,adis16490
> - adi,adis16495-1
> - adi,adis16495-2
prev parent reply other threads:[~2024-11-01 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 13:07 [PATCH 1/3] iio: imu: adis16480: add devices to adis16480 driver Darius Berghe
2024-11-01 13:07 ` [PATCH 2/3] iio: imu: adis16480: add devices to adis16480 - docs Darius Berghe
2024-11-01 13:07 ` [PATCH 3/3] dt-bindings: iio: adis16480: add devices to adis16480 Darius Berghe
2024-11-01 15:12 ` Jonathan Cameron [this message]
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=20241101151243.558a8577@jic23-huawei \
--to=jic23@kernel.org \
--cc=darius.berghe@analog.com \
--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