From: Jonathan Cameron <jic23@kernel.org>
To: Rodrigo Alencar <455.rodrigo.alencar@gmail.com>
Cc: "Alexander A. Klimov" <grandmaster@al2klimov.de>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Alexandru Ardelean" <alexandru.ardelean@analog.com>,
"Mircea Caprioru" <mircea.caprioru@analog.com>,
"open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iio: dac: ad5686: update of_match_table
Date: Fri, 22 May 2026 16:05:17 +0100 [thread overview]
Message-ID: <20260522160517.766c42f0@jic23-huawei> (raw)
In-Reply-To: <ba4tnwmwcqkovyq67ootyqxyqhzk4xd3crohdpv6so7nidjdgb@kgv5zi6aw2nw>
On Thu, 21 May 2026 09:18:24 +0100
Rodrigo Alencar <455.rodrigo.alencar@gmail.com> wrote:
> On 26/05/20 07:57PM, Alexander A. Klimov wrote:
> > When AD5673R/AD5677R support was added, of_match_table wasn't updated,
> > so these two devices couldn't be probed based on device tree contents
> > until now. I fixed this.
> >
> > Fixes: 477bd010c20e ("iio: dac: ad5686: Add support for AD5673R/AD5677R")
> > Signed-off-by: Alexander A. Klimov <grandmaster@al2klimov.de>
> > ---
> > drivers/iio/dac/ad5696-i2c.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/drivers/iio/dac/ad5696-i2c.c b/drivers/iio/dac/ad5696-i2c.c
> > index d3327bca0e07..fb118a02f76e 100644
> > --- a/drivers/iio/dac/ad5696-i2c.c
> > +++ b/drivers/iio/dac/ad5696-i2c.c
> > @@ -91,7 +91,9 @@ static const struct of_device_id ad5686_of_match[] = {
> > { .compatible = "adi,ad5337r" },
> > { .compatible = "adi,ad5338r" },
> > { .compatible = "adi,ad5671r" },
> > + { .compatible = "adi,ad5673r" },
> > { .compatible = "adi,ad5675r" },
> > + { .compatible = "adi,ad5677r" },
> > { .compatible = "adi,ad5691r" },
> > { .compatible = "adi,ad5692r" },
> > { .compatible = "adi,ad5693" },
> > --
> > 2.54.0
> >
>
> I am aware of this, but it is going to conflict with:
> https://lore.kernel.org/linux-iio/20260505-ad5686-fixes-v6-0-c2d5f7be32be@analog.com/
>
> This is also to be handled by follow up work:
> https://lore.kernel.org/all/20260422-ad5313r-iio-support-v1-1-ed7dca001d1b@analog.com/
> https://lore.kernel.org/all/20260422-ad5313r-iio-support-v1-9-ed7dca001d1b@analog.com/
>
> checkpatch would complain about this, once the dt-binding needs to come first.
>
I'll assume for now the fix will show up as part of Rodrigo's work.
Thanks
Jonathan
prev parent reply other threads:[~2026-05-22 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 17:57 Alexander A. Klimov
2026-05-21 8:18 ` Rodrigo Alencar
2026-05-22 15:05 ` 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=20260522160517.766c42f0@jic23-huawei \
--to=jic23@kernel.org \
--cc=455.rodrigo.alencar@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=alexandru.ardelean@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=grandmaster@al2klimov.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mircea.caprioru@analog.com \
--cc=nuno.sa@analog.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
all inboxes | Powered by JetHome®