public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Paller, Kim Seer" <KimSeer.Paller@analog.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"Mark Brown" <broonie@kernel.org>,
	"Dimitri Fedrau" <dima.fedrau@gmail.com>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Hennerich, Michael" <Michael.Hennerich@analog.com>,
	"Nuno Sá" <noname.nuno@gmail.com>
Subject: Re: [PATCH v2 3/5] dt-bindings: iio: dac: Add adi,ltc2664.yaml
Date: Sat, 25 May 2024 18:49:39 +0200	[thread overview]
Message-ID: <65019fa4-9e69-43b5-ac6c-c7607486cf69@kernel.org> (raw)
In-Reply-To: <PH0PR03MB71411D6F23D918723B9A5DA7F9F52@PH0PR03MB7141.namprd03.prod.outlook.com>

On 24/05/2024 08:28, Paller, Kim Seer wrote:
> 
>> -----Original Message-----
>> From: Krzysztof Kozlowski <krzk@kernel.org>
>> Sent: Thursday, May 23, 2024 2:40 PM
>> To: Paller, Kim Seer <KimSeer.Paller@analog.com>; linux-
>> kernel@vger.kernel.org; linux-iio@vger.kernel.org; devicetree@vger.kernel.org
>> Cc: Jonathan Cameron <jic23@kernel.org>; David Lechner
>> <dlechner@baylibre.com>; Lars-Peter Clausen <lars@metafoo.de>; Liam
>> Girdwood <lgirdwood@gmail.com>; Mark Brown <broonie@kernel.org>;
>> Dimitri Fedrau <dima.fedrau@gmail.com>; Krzysztof Kozlowski
>> <krzk+dt@kernel.org>; Rob Herring <robh@kernel.org>; Conor Dooley
>> <conor+dt@kernel.org>; Hennerich, Michael
>> <Michael.Hennerich@analog.com>; Nuno Sá <noname.nuno@gmail.com>
>> 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


  reply	other threads:[~2024-05-25 16:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23  3:19 [PATCH v2 0/5] Add driver for LTC2664 and LTC2672 Kim Seer Paller
2024-05-23  3:19 ` [PATCH v2 1/5] iio: ABI: Generalize ABI documentation for DAC Kim Seer Paller
2024-05-23 16:52   ` Jonathan Cameron
2024-05-23  3:19 ` [PATCH v2 2/5] iio: ABI: add DAC 42kohm_to_gnd powerdown mode Kim Seer Paller
2024-06-03 18:46   ` David Lechner
2024-05-23  3:19 ` [PATCH v2 3/5] dt-bindings: iio: dac: Add adi,ltc2664.yaml Kim Seer Paller
2024-05-23  6:39   ` Krzysztof Kozlowski
2024-05-24  6:28     ` Paller, Kim Seer
2024-05-25 16:49       ` Krzysztof Kozlowski [this message]
2024-05-25 17:17   ` Jonathan Cameron
2024-05-23  3:19 ` [PATCH v2 4/5] dt-bindings: iio: dac: Add adi,ltc2672.yaml Kim Seer Paller
2024-05-23  4:24   ` Rob Herring (Arm)
2024-05-23 12:33   ` Rob Herring
2024-05-23  3:19 ` [PATCH v2 5/5] iio: dac: ltc2664: Add driver for LTC2664 and LTC2672 Kim Seer Paller
2024-05-23 17:02   ` Jonathan Cameron
2024-05-28  5:53     ` Paller, Kim Seer
2024-06-02 13:13       ` Jonathan Cameron
2024-05-24  3:28   ` kernel test robot

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=65019fa4-9e69-43b5-ac6c-c7607486cf69@kernel.org \
    --to=krzk@kernel.org \
    --cc=KimSeer.Paller@analog.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dima.fedrau@gmail.com \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noname.nuno@gmail.com \
    --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