Re: [PATCH v4 2/4] dt-bindings: iio: dac: add adi,ad5710r.yaml

[Conor Dooley <conor@kernel.org>]

[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]

On Tue, Sep 01, 2026 at 04:14:08AM +0100, Jonathan Cameron wrote:
> 
> Hi Conor,
> 
> > > +  adi,range-double:
> > > +    description:
> > > +      Configure the output range for all channels. If the property is present,
> > > +      the output will range from 0V to 2 x Vref. If the property is not present,
> > > +      the output will range from 0V to Vref.  
> > 
> > What was the rationale provided for this not being a userspace control?
> > 
> Jumping in as I happen to read this...
> 
> For DACs we often do it in kernel as potentially there is a circuit dependent aspect.
> In extreme case leading to the bad kind of smoke. Normally it is covered by an
> output-range pair, but can't do that here as it is relative to vref (which
> we have no way of knowing in the binding). 
> 
> For input devices it is always a userspace thing to control.

I thought it'd actually be the opposite, with the assumption that output
devices would default to being off and so there wouldn't be smoke
production.
If you say it's normal, then fine :)

> 
> > > +    type: boolean

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]