From: Rob Herring <robh@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Peng Fan <peng.fan@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Cristian Marussi <cristian.marussi@arm.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH 1/3] dt-bindings: pinctrl: support i.MX95 SCMI pinctrl
Date: Mon, 15 Apr 2024 17:50:08 -0500 [thread overview]
Message-ID: <20240415225008.GA215835-robh@kernel.org> (raw)
In-Reply-To: <20240412-pinctrl-scmi-oem-v1-v1-1-704f242544c1@nxp.com>
On Fri, Apr 12, 2024 at 08:29:25AM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> i.MX95 Pinctrl is managed by SCMI firmware using OEM extensions. This
> patch is to add i.MX95 Pinctrl OEM extensions properties.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> .../bindings/pinctrl/nxp,imx95-pinctrl.yaml | 44 ++++++++++++++++++++++
> 1 file changed, 44 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/nxp,imx95-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/nxp,imx95-pinctrl.yaml
> new file mode 100644
> index 000000000000..4bf7a6192813
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pinctrl/nxp,imx95-pinctrl.yaml
> @@ -0,0 +1,44 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +# Copyright 2024 NXP
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/pinctrl/nxp,imx95-pinctrl.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: i.MX System Control and Management Interface (SCMI) Pinctrl Protocol
> +
> +maintainers:
> + - Peng Fan <peng.fan@arm.com>
> +
> +patternProperties:
> + '-pins$': false
Why?
> + 'grp$':
> + type: object
Missing 'additionalProperties: false'
> +
> + properties:
> + $nodename:
> + pattern: "^[0-9a-f]+$"
Drop. That has no effect. You just defined the nodename above.
> +
> + pins:
> + $ref: /schemas/types.yaml#/definitions/string
> + description: name of the pin
Needs to define the possible values.
> +
> + nxp,func-id:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: high impedance mode ("third-state", "floating")
We already have a standard property for high impendance. You should know
that since you obviously copied the description...
> +
> + nxp,pin-conf:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: latch weakly
Same here.
> +
> + nxp,daisy-id:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: pull up the pin. Takes as optional argument on hardware
> + supporting it the pull strength in Ohm.
And here...
> +
> + nxp,daisy-conf:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: pull down the pin. Takes as optional argument on hardware
> + supporting it the pull strength in Ohm.
And here...
> +
> +additionalProperties: true
>
> --
> 2.37.1
>
next prev parent reply other threads:[~2024-04-15 22:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 0:29 [PATCH 0/3] pinctrl: scmi: support i.MX95 OEM extensions Peng Fan (OSS)
2024-04-12 0:29 ` [PATCH 1/3] dt-bindings: pinctrl: support i.MX95 SCMI pinctrl Peng Fan (OSS)
2024-04-12 15:10 ` Frank Li
2024-04-13 5:56 ` Peng Fan
2024-04-15 22:50 ` Rob Herring [this message]
2024-04-15 23:17 ` Peng Fan
2024-04-12 0:29 ` [PATCH 2/3] dt-bindings: firmware: arm,scmi: support i.MX95 SCMI Pinctrl Peng Fan (OSS)
2024-04-12 15:11 ` Frank Li
2024-04-13 6:01 ` Peng Fan
2024-04-15 22:56 ` Rob Herring
2024-04-16 3:07 ` Peng Fan
2024-04-16 6:41 ` Peng Fan
2024-04-12 0:29 ` [PATCH 3/3] pinctrl: scmi: support i.MX OEM pin configuration type Peng Fan (OSS)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240415225008.GA215835-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@arm.com \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=sudeep.holla@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox