[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<PH0PR03MB7141297885946A5A77204567F9D82@PH0PR03MB7141.namprd03.prod.outlook.com>
Date: Thu, 20 Mar 2025 00:52:30 +0000
From: "Paller, Kim Seer" <KimSeer.Paller@...log.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
CC: Jonathan Cameron <jic23@...nel.org>, Lars-Peter Clausen <lars@...afoo.de>,
"Hennerich, Michael" <Michael.Hennerich@...log.com>,
Rob Herring
<robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley
<conor+dt@...nel.org>,
"linux-iio@...r.kernel.org"
<linux-iio@...r.kernel.org>,
"linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org"
<devicetree@...r.kernel.org>
Subject: RE: [PATCH 3/4] dt-bindings: iio: dac: Add adi,ad3530r.yaml
> > + adi,double-output-range:
> > + description:
> > + Configure the output range for all channels. If the property is present,
> > + the output will range from 0V to 2Vref. If the property is not
> > + present, the output will range from 0V to Vref.
>
> You already have adi,range-double. It's not us who should find it, but
> you. You have just ADI bindings to look at. We have all bindings.
Apologies, I'll take note of this. Thanks
Powered by blists - more mailing lists