[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <df1895c8-aec6-cada-e208-ccda8042860d@baylibre.com>
Date: Fri, 21 Oct 2022 14:54:10 +0200
From: Amjad Ouled-Ameur <aouledameur@...libre.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
neil.armstrong@...aro.org, Mark Brown <broonie@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Jerome Brunet <jbrunet@...libre.com>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
Kevin Hilman <khilman@...libre.com>,
Rob Herring <robh+dt@...nel.org>
Cc: Da Xue <da@...re.computer>, linux-arm-kernel@...ts.infradead.org,
devicetree@...r.kernel.org, linux-amlogic@...ts.infradead.org,
linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/2] spi: dt-bindings: amlogic, meson-gx-spicc: Add
pinctrl names for SPI signal states
Hi
On 10/20/22 14:49, Krzysztof Kozlowski wrote:
>>>> + properties:
>>>> + pinctrl-names:
>>>> + minItems: 1
>>>> + items:
>>>> + - const: default
>>>> + - const: idle-high
>>>> + - const: idle-low
>>> You should also define in such case pinctrl-0 and others.
>> Ok I thought it would be covered by the pinctrl-consumer.yaml
>> but yeah we should allow pinctrl-1 and pinctrl-2 here aswell by adding:
>>
>> pinctrl-1: true
>> pinctrl-2: true
>>
>>
In such case, should I define pinctrl- as part of the if statement, as shown below,
or before allOf ?
[...]
- if:
properties:
compatible:
contains:
enum:
- amlogic,meson-gx-spicc
then:
properties:
pinctrl-0: true
pinctrl-1: true
pinctrl-2: true
pinctrl-names:
minItems: 1
items:
- const: default
- const: idle-high
- const: idle-low
[...]
Regards
Amjad
> Yes.
>
> Best regards,
> Krzysztof
>
Powered by blists - more mailing lists