From: David Lechner <dlechner@baylibre.com>
To: "Miclaus, Antoniu" <Antoniu.Miclaus@analog.com>,
"jic23@kernel.org" <jic23@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>
Cc: Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v7 7/8] dt-bindings: iio: adc: add ad4851
Date: Mon, 9 Dec 2024 11:44:14 -0600 [thread overview]
Message-ID: <4be8bebb-7db3-43e5-b00e-95ebf7114d80@baylibre.com> (raw)
In-Reply-To: <CY4PR03MB3399F17206B01006467B602F9B3C2@CY4PR03MB3399.namprd03.prod.outlook.com>
On 12/9/24 8:02 AM, Miclaus, Antoniu wrote:
>
>
> --
> Antoniu Miclăuş
>
>> -----Original Message-----
>> From: David Lechner <dlechner@baylibre.com>
>> Sent: Thursday, December 5, 2024 2:46 AM
>> To: Miclaus, Antoniu <Antoniu.Miclaus@analog.com>; jic23@kernel.org;
>> robh@kernel.org; conor+dt@kernel.org; linux-iio@vger.kernel.org;
>> devicetree@vger.kernel.org; linux-kernel@vger.kernel.org; linux-
>> pwm@vger.kernel.org
>> Cc: Conor Dooley <conor.dooley@microchip.com>
>> Subject: Re: [PATCH v7 7/8] dt-bindings: iio: adc: add ad4851
>>
>> [External]
>>
>> On 11/29/24 9:35 AM, Antoniu Miclaus wrote:
>>> Add devicetree bindings for ad485x family.
>>>
>>> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
>>> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
>>> ---
>>> changes in v7:
>>> - add adc channels support
>>
>> What is the reason for this change? In a previous version of this series,
>> you explained that we didn't want to specify diff-channels in the DT
>> because there was a use case to use channels as both single-ended and
>> differential at runtime. So I am surprised to see this being added now.
>>
> We had a discussion and we decided to go for the dt approach for specifying
> the channels configuration, even though in the first place we wanted to avoid this.
> Overall it makes more sense.
OK, in that case we will also want to make use of the standard "bipolar"
property from adc.yaml as well since the chip differentiates between
unipolar and bipolar inputs.
Also, might want to drop Conor's review tag and give an explanation in
the next revision since adding these channel properties is a bit of
a big change compared to the version he reviewed.
>
>>> +patternProperties:
>>> + "^channel(@[0-7])?$":
>>> + $ref: adc.yaml
>>> + type: object
>>> + description: Represents the channels which are connected to the ADC.
>>> +
>>> + properties:
>>> + reg:
>>> + description: The channel number in single-ended mode.
>>> + minimum: 0
>>> + maximum: 7
>>> +
>>> + diff-channels: true
>>> +
>>> + required:
>>> + - reg
>>> +
>>> + additionalProperties: false
>>> +
next prev parent reply other threads:[~2024-12-09 17:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 15:35 [PATCH v7 0/8] Add support for AD485x DAS Family Antoniu Miclaus
2024-11-29 15:35 ` [PATCH v7 1/8] iio: backend: add API for interface get Antoniu Miclaus
2024-11-29 15:35 ` [PATCH v7 2/8] iio: backend: add support for data size set Antoniu Miclaus
2024-11-29 15:35 ` [PATCH v7 3/8] iio: backend: add API for oversampling Antoniu Miclaus
2024-12-05 0:44 ` David Lechner
2024-11-29 15:35 ` [PATCH v7 4/8] iio: adc: adi-axi-adc: add interface type Antoniu Miclaus
2024-11-29 15:35 ` [PATCH v7 5/8] iio: adc: adi-axi-adc: set data format Antoniu Miclaus
2024-12-05 0:45 ` David Lechner
2024-12-09 13:58 ` Miclaus, Antoniu
2024-11-29 15:35 ` [PATCH v7 6/8] iio: adc: adi-axi-adc: add oversampling Antoniu Miclaus
2024-11-29 15:35 ` [PATCH v7 7/8] dt-bindings: iio: adc: add ad4851 Antoniu Miclaus
2024-12-05 0:46 ` David Lechner
2024-12-09 14:02 ` Miclaus, Antoniu
2024-12-09 17:44 ` David Lechner [this message]
2024-11-29 15:35 ` [PATCH v7 8/8] iio: adc: ad4851: add ad485x driver Antoniu Miclaus
2024-11-30 11:19 ` kernel test robot
2024-11-30 17:06 ` Jonathan Cameron
2024-12-05 0:47 ` David Lechner
2024-12-07 15:29 ` Uwe Kleine-König
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=4be8bebb-7db3-43e5-b00e-95ebf7114d80@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Antoniu.Miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--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