The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: Denny Lin <dennylin0707@gmail.com>,
	lars@metafoo.de, Michael.Hennerich@analog.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, nuno.sa@analog.com,
	andy@kernel.org, linux-iio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/1] dt-bindings: iio: adc: add AD7816/AD7817/AD7818 binding
Date: Tue, 12 May 2026 12:22:05 +0100	[thread overview]
Message-ID: <20260512122205.07733eff@jic23-huawei> (raw)
In-Reply-To: <f9469c48-ea67-4106-a577-4818cf3dd51d@baylibre.com>

On Mon, 11 May 2026 11:31:13 -0500
David Lechner <dlechner@baylibre.com> wrote:

> On 5/11/26 11:23 AM, Denny Lin wrote:
> > On Mon, May 11, 2026 at 7:51 AM David Lechner <dlechner@baylibre.com> wrote:  
> >>
> >> Usually, we want to be moving the drivers out of staging when
> >> adding the DT bindings so that it all gets reviewed for correctness
> >> at the same time.
> >>
> >> Drivers in staging are usually there because they are doing things
> >> that are not actually acceptable for the final stable mainline
> >> version of a driver and need more work.
> >>  
> > 
> > Thanks for the explanation.
> > 
> > I took a look at the driver and noticed it still uses the older
> > IIO sysfs-based interface rather than the iio_chan_spec + read_raw
> > model.
> > 
> > Would you recommend updating the driver first, or is it okay to
> > proceed with the binding separately?
> > 
> > Thanks,
> > Hungyu  
> 
> ADI's website says that these parts are obsolete, so unless anyone is
> actually still using these with a mainline kernel, I would suggest that
> we drop the driver rather than spending time fixing it up.

The ad7817 isn't obsolete yet unfortunately - that's the only reason I didn't
drop this last time I checked..

Any Analog folk want to take a view on this one - particularly if you
can check if it will be going obsolete soon.   Good not to waste Denny's
time on this if so!

J

> 
> In any case, unless you have the hardware for testing, it would be
> best not to make significant changes. There is a non-standard "oti"
> attribute that we would need to figure out what to do with. This is
> likely why the driver is in staging in the first place.


  reply	other threads:[~2026-05-12 11:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-09  2:27 [PATCH v3 0/1] dt-bindings: iio: adc: add AD7816/AD7817/AD7818 binding Hungyu Lin
2026-05-09  2:27 ` [PATCH v3 1/1] " Hungyu Lin
2026-05-09 22:13   ` David Lechner
2026-05-10  1:37     ` Denny Lin
2026-05-11 14:51       ` David Lechner
2026-05-11 16:23         ` Denny Lin
2026-05-11 16:31           ` David Lechner
2026-05-12 11:22             ` Jonathan Cameron [this message]
2026-05-11 16:52   ` Jonathan Cameron
2026-05-09 22:21 ` [PATCH v3 0/1] " David Lechner

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=20260512122205.07733eff@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=dennylin0707@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox