[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6aae4d40-e922-4e63-02a4-e56385af6069@linaro.org>
Date: Mon, 28 Aug 2023 14:30:33 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Tomer Maimon <tmaimon77@...il.com>
Cc: linus.walleij@...aro.org, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
avifishman70@...il.com, tali.perry1@...il.com, joel@....id.au,
venture@...gle.com, yuenn@...gle.com, benjaminfair@...gle.com,
j.neuschaefer@....net, openbmc@...ts.ozlabs.org,
linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Rob Herring <robh@...nel.org>
Subject: Re: [PATCH v6 1/2] dt-binding: pinctrl: Add NPCM8XX pinctrl and GPIO
documentation
On 28/08/2023 13:43, Tomer Maimon wrote:
>>
>>> Which leds to second
>>> question - how pinctrl could have @0? It's already taken by SoC! So your
>>> DTS here - unit address and ranges - are clearly wrong.
>>>
>>>
>>>> BTW, I have run both dt_binding_check and W=1 dtbs_check, and didn't
>>>> see an issue related to the pinctrl: pinctrl@...00260, do I need to
>>>> add another flag to see the issue?
>>>
>>> Did you read my message last time? I said - it's about DTS, not the binding.
> yes, understood doesn't the dtbs_check check the DTS?
Yes, it does, and the first error is being reported (just like several
others for your DTS...). The second about gpio node, I think is not.
Best regards,
Krzysztof
Powered by blists - more mailing lists