[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f63fcb88-77de-0d57-f3f4-5d61a6d4c133@linaro.org>
Date: Sun, 11 Sep 2022 15:26:26 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Iskren Chernev <iskren.chernev@...il.com>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...ainline.org>,
Linus Walleij <linus.walleij@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Rajendra Nayak <rnayak@...eaurora.org>,
Martin Botka <martin.botka@...ainline.org>,
Vinod Koul <vkoul@...nel.org>, linux-arm-msm@...r.kernel.org,
linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 01/40] dt-bindings: pinctrl: qcom,sm6115-pinctrl: fix
matching pin config
On 11/09/2022 14:59, Iskren Chernev wrote:
>
>
>
> On 9/11/22 14:11, Krzysztof Kozlowski wrote:
>> Matching PMIC GPIOs config nodes within a '-state' node by '.*' pattern
>> does not work as expected because of linux,phandle in the DTB:
>>
>> 'pins' is a required property
>> 'function' is a required property
>> 'rx', 'tx' do not match any of the regexes: 'pinctrl-[0-9]+'
>> [[59]] is not of type 'object'
>>
>> Make the schema stricter and expect such nodes to be either named
>> 'pinconfig' or followed with '-pins' prefix.
>
> Well, now you don't allow pinconfig, so maybe tweak the commit message.
True, thanks!
Best regards,
Krzysztof
Powered by blists - more mailing lists