On 24/05/2024 08:28, Paller, Kim Seer wrote: > >> -----Original Message----- >> From: Krzysztof Kozlowski <krzk@xxxxxxxxxx> >> Sent: Thursday, May 23, 2024 2:40 PM >> To: Paller, Kim Seer <KimSeer.Paller@xxxxxxxxxx>; linux- >> kernel@xxxxxxxxxxxxxxx; linux-iio@xxxxxxxxxxxxxxx; devicetree@xxxxxxxxxxxxxxx >> Cc: Jonathan Cameron <jic23@xxxxxxxxxx>; David Lechner >> <dlechner@xxxxxxxxxxxx>; Lars-Peter Clausen <lars@xxxxxxxxxx>; Liam >> Girdwood <lgirdwood@xxxxxxxxx>; Mark Brown <broonie@xxxxxxxxxx>; >> Dimitri Fedrau <dima.fedrau@xxxxxxxxx>; Krzysztof Kozlowski >> <krzk+dt@xxxxxxxxxx>; Rob Herring <robh@xxxxxxxxxx>; Conor Dooley >> <conor+dt@xxxxxxxxxx>; Hennerich, Michael >> <Michael.Hennerich@xxxxxxxxxx>; Nuno Sá <noname.nuno@xxxxxxxxx> >> Subject: Re: [PATCH v2 3/5] dt-bindings: iio: dac: Add adi,ltc2664.yaml >> >> [External] >> >> On 23/05/2024 05:19, Kim Seer Paller wrote: >>> Add documentation for ltc2664. >>> >> >> >>> + >>> + ref-supply: >>> + description: >>> + Reference Input/Output. The voltage at the REF pin sets the full-scale >>> + range of all channels. If not provided the internal reference is used and >>> + also provided on the VREF pin. >>> + >>> + clr-gpios: >>> + description: >>> + Active-low Asynchronous Clear Input. A logic low at this level-triggered >>> + input clears the part to the reset code and range determined by the >>> + hardwired option chosen using the MSPAN pins. The control registers are >>> + cleared to zero. >> >> So this is a reset gpio? > > Yes, this is a reset gpio. Then call it that - reset-gpios (see gpio-consumer-common). Best regards, Krzysztof
