From: Conor Dooley <conor@kernel.org>
To: Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: "Nuno Sá" <nuno.sa@analog.com>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: iio: dac: Document AD5446 and similar devices
Date: Fri, 24 Oct 2025 12:04:58 +0100 [thread overview]
Message-ID: <20251024-scope-uncle-93183d40ef11@spud> (raw)
In-Reply-To: <20251024111207.00007427@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1501 bytes --]
On Fri, Oct 24, 2025 at 11:12:07AM +0100, Jonathan Cameron wrote:
> On Thu, 23 Oct 2025 19:24:17 +0100
> Conor Dooley <conor@kernel.org> wrote:
>
> > On Thu, Oct 23, 2025 at 02:01:37PM +0300, Nuno Sá wrote:
> > > Add device tree binding documentation for the Analog Devices AD5446
> > > family of Digital-to-Analog Converters and compatible devices from
> > > Texas Instruments. There's both SPI and I2C interfaces and feature
> > > resolutions ranging from 8-bit to 16-bit.
> > >
> > > The binding covers 29 compatible devices including the AD5446 series,
> >
> > If they're compatible, how come there's no fallback use? Just to keep
> > things consistent with how they've always been while probing as spi
> > child devices?
> Hi Conor,
>
> They aren't compatible. The 2nd patch is misleading because it doesn't
> associate data with the of_device_id. The driver is getting that from
> matching the compatible property with manufacturer stripped off.
>
> I've requested Nuno sort that out in v3. It's a bit more than just
> adding the data as would also involve moving away from using an enum
> to using pointers to the structures that the enum indexes (currently in
> an array).
>
> https://elixir.bootlin.com/linux/v6.17.4/source/drivers/iio/dac/ad5446.c#L315
>
Right, I think the wording about "compatible" should be removed from the
commit message here then. Maybe something like "derivative devices"
would be a better fit?
pw-bot: changes-requested
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-10-24 11:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 11:01 [PATCH v2 0/3] iio: dac: ad5446: Add AD5542 to the spi id table Nuno Sá
2025-10-23 11:01 ` [PATCH v2 1/3] dt-bindings: iio: dac: Document AD5446 and similar devices Nuno Sá
2025-10-23 17:08 ` Jonathan Cameron
2025-10-27 14:48 ` Nuno Sá
2025-10-27 15:01 ` Jonathan Cameron
2025-10-30 11:30 ` Nuno Sá
2025-11-02 12:13 ` Jonathan Cameron
2025-10-23 18:24 ` Conor Dooley
2025-10-24 10:12 ` Jonathan Cameron
2025-10-24 11:04 ` Conor Dooley [this message]
2025-10-27 14:49 ` Nuno Sá
2025-10-23 11:01 ` [PATCH v2 2/3] iio: dac: ad5456: Add missing DT compatibles Nuno Sá
2025-10-23 17:13 ` Jonathan Cameron
2025-10-27 14:55 ` Nuno Sá
2025-10-24 16:29 ` Andy Shevchenko
2025-10-24 18:41 ` Jonathan Cameron
2025-10-23 11:01 ` [PATCH v2 3/3] iio: dac: ad5446: Add AD5542 to the spi id table 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=20251024-scope-uncle-93183d40ef11@spud \
--to=conor@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.