[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1fa6128f-03c1-4f41-8dff-4191893f460c@linaro.org>
Date: Tue, 19 Dec 2023 09:51:31 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Anshul Dalal <anshulusr@...il.com>, linux-kernel@...r.kernel.org,
linux-iio@...r.kernel.org, devicetree@...r.kernel.org
Cc: Conor Dooley <conor+dt@...nel.org>, Lars-Peter Clausen <lars@...afoo.de>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
linux-kernel-mentees@...ts.linuxfoundation.org,
Shuah Khan <skhan@...uxfoundation.org>,
Conor Dooley <conor.dooley@...rochip.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: iio: dac: add MCP4821
On 19/12/2023 09:42, Anshul Dalal wrote:
> On 12/19/23 13:29, Krzysztof Kozlowski wrote:
>> On 18/12/2023 17:47, Anshul Dalal wrote:
>>> +
>>> + reg:
>>> + maxItems: 1
>>> +
>>> + vdd-supply: true
>>> +
>>> + ldac-gpios:
>>> + description: |
>>> + Active Low LDAC (Latch DAC Input) pin used to update the DAC output.
>>> + maxItems: 1
>>> +
>>> + shdn-gpios:
>>
>> Open gpio-consumer-common.yaml and look at entries there.
>>
>
> Should I name the property `powerdown-gpios` instead of `shdn-gpios` as
> specified in gpio-consumer-common.yaml?
Yes. You can provide the name of actual pin in description.
> Furthermore, do I need to add gpio-consumer-common.yaml as a ref?
No.
Best regards,
Krzysztof
Powered by blists - more mailing lists