Messages in this thread | | | From | Rob Herring <> | Date | Tue, 14 Jul 2020 08:05:37 -0600 | Subject | Re: [PATCH RESEND v2] dt-bindings: pinctrl: Convert ingenic,pinctrl.txt to YAML |
| |
On Mon, Jul 13, 2020 at 9:36 AM Paul Cercueil <paul@crapouillou.net> wrote: > > Hi Rob, > > Le lun. 13 juil. 2020 à 9:32, Rob Herring <robh@kernel.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@crapouillou.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.
No such thing. There's a set of common properties, but that is all. You still need to document which properties apply because it is doubtful they all do.
> 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).
Ideally, the nodes should be named something we can match on like "-pins$", but if not you can do:
additionalProperties: type: object $ref: pincfg-node.yaml# properties: bias-disable: true ... additionalProperties: false
Rob
| |