Re: [PATCH 1/6] dt-bindings: iio: adc: Add AD7768
From: David Lechner
Date: Sun Jul 12 2026 - 12:07:51 EST
On 7/11/26 8:39 PM, Jonathan Cameron wrote:
> On Sat, 11 Jul 2026 09:40:32 -0500
> David Lechner <dlechner@xxxxxxxxxxxx> wrote:
>
>> On 7/9/26 7:33 PM, Jonathan Cameron wrote:
>>>>> + adi,common-mode-output:
>>>>> + $ref: /schemas/types.yaml#/definitions/string
>>>>> + enum:
>>>>> + - avdd-avss-half
>>>>> + - 1.65V
>>>>> + - 2.5V
>>>>> + - 2.14V
>>>>> + description:
>>>>> + Common mode voltage output selection.
>>>>
>>>> Why not using standard regulator provider bindings for this?
>>>
>>> Interesting question. If that was done there would need to be
>>> a consumer which means explicit modelling of any analog circuit.
>>> We do that in a few cases but so far (and yup this is a driver thing
>>> in a dt-binding) I don't think we have any way to consumer data when
>>> a backend is involved.
>>
>> There is also the regulator-always-on property, so strictly speaking,
>> a consumer is not required.
>
> Makes some sense I guess.
>
> How would the voltage be controlled? Set min and max to same value?
yes
>
> J
>>
>>>
>>>>
>>>>> +
>>>>> + adi,vcm-power-down:
>>>>> + type: boolean
>>>>> + description: Power down the common mode output buffer
>>>>
>>>> Is the buffer separate from the output? In that case I would expect
>>>> buffer to be in the property name, otherwise this should just be
>>>> part of the enum options above (and the default one at that).
>>>>
>>
>