[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240711223618.GA3237343-robh@kernel.org>
Date: Thu, 11 Jul 2024 16:36:18 -0600
From: Rob Herring <robh@...nel.org>
To: Sai Krishna Potthuri <sai.krishna.potthuri@....com>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Michal Simek <michal.simek@....com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Jay Buddhabhatti <jay.buddhabhatti@....com>,
Dhaval Shah <dhaval.r.shah@....com>,
Praveen Teja Kundanala <praveen.teja.kundanala@....com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
saikrishna12468@...il.com, git@....com
Subject: Re: [PATCH 1/3] dt-bindings: pinctrl: Add support for Xilinx Versal
platform
On Thu, Jul 11, 2024 at 04:03:15PM +0530, Sai Krishna Potthuri wrote:
> Add Xilinx Versal compatible string and corresponding groups, function and
> pins properties to support pin controller features on Versal platform.
>
> Signed-off-by: Sai Krishna Potthuri <sai.krishna.potthuri@....com>
> ---
> .../bindings/pinctrl/xlnx,zynqmp-pinctrl.yaml | 509 +++++++++++-------
> 1 file changed, 329 insertions(+), 180 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/xlnx,zynqmp-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/xlnx,zynqmp-pinctrl.yaml
> index ce66fd15ff9c..68c378b17f49 100644
> --- a/Documentation/devicetree/bindings/pinctrl/xlnx,zynqmp-pinctrl.yaml
> +++ b/Documentation/devicetree/bindings/pinctrl/xlnx,zynqmp-pinctrl.yaml
> @@ -28,7 +28,9 @@ description: |
>
> properties:
> compatible:
> - const: xlnx,zynqmp-pinctrl
> + enum:
> + - xlnx,zynqmp-pinctrl
> + - xlnx,versal-pinctrl
>
> patternProperties:
> '^(.*-)?(default|gpio-grp)$':
> @@ -46,196 +48,334 @@ patternProperties:
> description:
> List of pins to select (either this or "groups" must be specified)
> items:
> - pattern: '^MIO([0-9]|[1-6][0-9]|7[0-7])$'
> + allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: xlnx,zynqmp-pinctrl
> + then:
> + pattern: '^MIO([0-9]|[1-6][0-9]|7[0-7])$'
> + else:
> + pattern: '^((LPD|PMC)_)?MIO([0-9]|[1-6][0-9]|7[0-7])$'
Did you test whether this works? It doesn't because the schema is
nonsense. The schema applies to a property's value, but the "if" schema
applies to a node. And it's not even the node you are at, but the parent
node. IOW, there is no "compatible" in this node.
The 'else' schema covers both cases, so I'd just change the pattern and
be done with it.
However, based on the rest of the patch, you should just do a new schema
doc. There's little overlap of the values.
Rob
Powered by blists - more mailing lists