From: David Leonard <David.Leonard@digi.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Dong Aisheng <aisheng.dong@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
Shawn Guo <shawnguo@kernel.org>, Jacky Bai <ping.bai@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 6/6] dt-bindings: pinctrl: Add fsl,ls1046a-pinctrl yaml file
Date: Tue, 27 Aug 2024 12:15:08 +1000 (AEST) [thread overview]
Message-ID: <b17a0414-8503-950e-a133-e5a1b1cab8c4@digi.com> (raw)
Add a binding schema and examples for the LS1046A's pinctrl function.
Signed-off-by: David Leonard <David.Leonard@digi.com>
---
.../bindings/pinctrl/fsl,ls1046a-pinctrl.yaml | 74 +++++++++++++++++++
1 file changed, 74 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,ls1046a-pinctrl.yaml
diff --git a/Documentation/devicetree/bindings/pinctrl/fsl,ls1046a-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/fsl,ls1046a-pinctrl.yaml
new file mode 100644
index 000000000000..3d49e42d33e8
--- /dev/null
+++ b/Documentation/devicetree/bindings/pinctrl/fsl,ls1046a-pinctrl.yaml
@@ -0,0 +1,74 @@
+# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/pinctrl/fsl,ls1046a-pinctrl.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: NXP QorIQ LS1046A pin multiplexing
+
+maintainers:
+ - David.Leonard@digi.com
+
+description: >
+ Bindings for LS1046A pinmux control.
+
+properties:
+ compatible:
+ const: fsl,ls1046a-pinctrl
+
+ reg:
+ description: >
+ Specifies the base address of SCFG_RCWPMUXCR0
+ maxItems: 2
+
+ big-endian:
+ description: >
+ If present, the register is implemented in big endian mode.
+ type: boolean
+
+patternProperties:
+ '^pinctrl-':
+ type: object
+ $ref: pinmux-node.yaml#
+ unevaluatedProperties: false
+
+ properties:
+ function:
+ enum: [ i2c, gpio, evt, usb, ftm ]
+
+ groups:
+ items:
+ enum: [ L4, M4, M3, N3 ]
+
+allOf:
+ - $ref: pinctrl.yaml#
+
+required:
+ - compatible
+ - reg
+
+additionalProperties: false
+
+examples:
+ - |
+ pinmux: pinmux@157040c {
+ compatible = "fsl,ls1046a-pinctrl";
+ reg = <0 0x157040c 0 4>;
+ big-endian;
+ pinctrl_i2c2: pinctrl-i2c2 {
+ groups = "L4", "M4";
+ function = "i2c";
+ };
+ pinctrl_i2c2_gpio: pinctrl-i2c2-gpio3 {
+ groups = "L4", "M4";
+ function = "gpio";
+ };
+ pinctrl_i2c3: pinctrl-i2c3 {
+ groups = "M3", "N3";
+ function = "i2c";
+ };
+ pinctrl_i2c3_gpio: pinctrl-i2c3-gpio {
+ groups = "M3", "N3";
+ function = "gpio";
+ };
+ };
--
2.43.0
next reply other threads:[~2024-08-27 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 2:15 David Leonard [this message]
2024-08-27 3:22 ` Rob Herring (Arm)
2024-08-27 6:20 ` Krzysztof Kozlowski
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=b17a0414-8503-950e-a133-e5a1b1cab8c4@digi.com \
--to=david.leonard@digi.com \
--cc=aisheng.dong@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--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=ping.bai@nxp.com \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
/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
all inboxes | Powered by JetHome®