Devicetree
 help / color / mirror / Atom feed
From: David Lechner <dlechner@baylibre.com>
To: Denny Lin <dennylin0707@gmail.com>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
	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: Mon, 11 May 2026 09:51:25 -0500	[thread overview]
Message-ID: <3493d6ef-5f02-4eb1-b81a-89597045acbb@baylibre.com> (raw)
In-Reply-To: <CAGEkeHfeZWi99TMvkXHhMSrUS8PshuekqjszBXaS39VsLUZ4eA@mail.gmail.com>

On 5/9/26 8:37 PM, Denny Lin wrote:
> Hi David,
> 
>> Why are we adding bindings without a driver to use them?
> 
> There is already a driver for these devices in
> drivers/staging/iio/adc/ad7816.c, which includes OF match entries
> for "adi,ad7816", "adi,ad7817", and "adi,ad7818".
> 
> This binding is intended to document the existing DT interface.

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,
> Hungyu
> 
> On Sat, May 9, 2026 at 3:13 PM David Lechner <dlechner@baylibre.com> wrote:
>>
>> On 5/8/26 9:27 PM, Hungyu Lin wrote:
>>> Add Device Tree binding documentation for the Analog Devices
>>> AD7816, AD7817 and AD7818 SPI ADC devices.
>>>
>> Why are we adding bindings without a driver to use them?


  reply	other threads:[~2026-05-11 14:51 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 [this message]
2026-05-11 16:23         ` Denny Lin
2026-05-11 16:31           ` David Lechner
2026-05-12 11:22             ` Jonathan Cameron
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=3493d6ef-5f02-4eb1-b81a-89597045acbb@baylibre.com \
    --to=dlechner@baylibre.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=dennylin0707@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --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