[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <459fe67d-0602-41c5-a94c-d9e9697c80b4@kernel.org>
Date: Wed, 26 Feb 2025 08:19:58 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Clement LE GOFFIC <clement.legoffic@...s.st.com>,
Linus Walleij <linus.walleij@...aro.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Bartosz Golaszewski <brgl@...ev.pl>
Cc: linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
devicetree@...r.kernel.org, linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/9] dt-bindings: pinctrl: stm32: Add HDP includes for
stm32mp platforms
On 25/02/2025 16:46, Clement LE GOFFIC wrote:
>>
>> Why this is a string not a number?
>>
>> Where is it used? I don't see usage in the driver, so this does not look
>> like binding (and DTS is not a driver).
>
> Those files are helpers for the devicetrees and may be included in
> stm32mp*-pinctrl.dtsi files.
So not a binding, see other platforms/header files how it is done.
> It is a string because it is an helper for the `function` property of
> `pinmux-node.yaml` which is a string.
>
> I understand that having a number as a string is not easily understandable.
> I'll consider it in a V2 by trying to use the `pinmux` property.
Let's keep discussing this part in the bindings doc patch.
Best regards,
Krzysztof
Powered by blists - more mailing lists