[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <ADZEDQ.ZXJ99TAYD15S2@crapouillou.net>
Date: Mon, 13 Jul 2020 17:36:46 +0200
From: Paul Cercueil <paul@...pouillou.net>
To: Rob Herring <robh@...nel.org>
Cc: Linus Walleij <linus.walleij@...aro.org>, od@...c.me,
linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND v2] dt-bindings: pinctrl: Convert
ingenic,pinctrl.txt to YAML
Hi Rob,
Le lun. 13 juil. 2020 à 9:32, Rob Herring <robh@...nel.org> a écrit :
> On Mon, Jun 22, 2020 at 01:37:40PM +0200, Paul Cercueil wrote:
>> Convert the ingenic,pinctrl.txt doc file to ingenic,pinctrl.yaml.
>>
>> In the process, some compatible strings now require a fallback, as
>> the
>> corresponding SoCs are pin-compatible with their fallback variant.
>>
>> Signed-off-by: Paul Cercueil <paul@...pouillou.net>
>> ---
>>
>> Notes:
>> v2: - Use 'pinctrl' instead of 'pin-controller' as the node name
>> - remove 'additionalProperties: false' since we will have
>> pin conf nodes
>
> What do those look like? They need to be described, but that can be a
> follow-up.
These are generic conf nodes that are handled by the pinctrl core.
Nothing specific to the hardware described here. The subnodes don't
have any specific pattern so it is not possible to represent them in
devicetree (we'd need a 'catch them all' wildcard pattern property).
Cheers,
-Paul
Powered by blists - more mailing lists