[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdaBV81OCwHuFCObwv_t55B9ANHaF5jEc=oorZdjpey0Ug@mail.gmail.com>
Date: Fri, 10 Dec 2021 00:30:13 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Wells Lu <wellslutw@...il.com>
Cc: linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
robh+dt@...nel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, wells.lu@...plus.com,
dvorkin@...bo.com
Subject: Re: [PATCH v3 1/2] dt-bindings: pinctrl: Add dt-bindings for Sunplus SP7021
On Tue, Dec 7, 2021 at 5:17 AM Wells Lu <wellslutw@...il.com> wrote:
> Add dt-bindings header files and documentation for Sunplus SP7021 SoC.
>
> Signed-off-by: Wells Lu <wellslutw@...il.com>
> +patternProperties:
> + '-pins$':
> + if:
> + type: object
> + then:
> + description: |
> + A pinctrl node should contain at least one subnodes representing the
> + pins or function-pins group available on the machine. Each subnode
> + will list the pins it needs, and how they should be configured.
> +
> + Pinctrl node's client devices use subnodes for desired pin
> + configuration. Client device subnodes use below standard properties.
I don't understand this if type object stuff here, Rob, help...
> + properties:
> + pins:
> + description: |
> + Define pins which are used by pinctrl node's client device.
(...)
> + $ref: /schemas/types.yaml#/definitions/uint32-array
Why can this not $ref the standard binings in
Documentation/devicetree/bindings/pinctrl/pinmux-node.yaml
See for example
Documentation/devicetree/bindings/pinctrl/actions,s500-pinctrl.yaml
for a nice example of how to use this.
Yours,
Linus Walleij
Powered by blists - more mailing lists