From: "Rafał Miłecki" <zajec5@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: "Tony Lindgren" <tony@atomide.com>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Florian Fainelli" <f.fainelli@gmail.com>,
bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: [PATCH V3 2/2] dt-bindings: pinctrl: brcm, ns-pinmux: describe pins, groups & functions
Date: Fri, 10 Dec 2021 12:42:22 +0100 [thread overview]
Message-ID: <20211210114222.26581-3-zajec5@gmail.com> (raw)
In-Reply-To: <20211210114222.26581-1-zajec5@gmail.com>
From: Rafał Miłecki <rafal@milecki.pl>
Use and extend generic pinctrl binding to include info about pins,
groups & functions.
Northstar platform pins have numbers assigned to them (they are needed
for mux programming) so add a custom "number" property for that.
Extend example to provide a complete binding of a single / random
function.
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
---
.../bindings/pinctrl/brcm,ns-pinmux.yaml | 38 ++++++++++++++++++-
1 file changed, 37 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/pinctrl/brcm,ns-pinmux.yaml b/Documentation/devicetree/bindings/pinctrl/brcm,ns-pinmux.yaml
index 8d1e5b1cdd5f..82d3e52a2229 100644
--- a/Documentation/devicetree/bindings/pinctrl/brcm,ns-pinmux.yaml
+++ b/Documentation/devicetree/bindings/pinctrl/brcm,ns-pinmux.yaml
@@ -30,6 +30,20 @@ properties:
reg-names:
const: cru_gpio_control
+ pins:
+ type: object
+
+ patternProperties:
+ "^.*$":
+ type: object
+
+ properties:
+ number:
+ description: Pin number
+ $ref: /schemas/types.yaml#/definitions/uint32
+
+ unevaluatedProperties: false
+
patternProperties:
'-pins$':
type: object
@@ -74,7 +88,7 @@ required:
- reg
- reg-names
-additionalProperties: false
+unevaluatedProperties: false
examples:
- |
@@ -83,6 +97,28 @@ examples:
reg = <0x1800c1c0 0x24>;
reg-names = "cru_gpio_control";
+ pins {
+ i2c_scl: i2c_scl {
+ number = <4>;
+ };
+
+ i2c_sda: i2c_sda {
+ number = <5>;
+ };
+ };
+
+ groups {
+ i2c_grp: i2c_grp {
+ pins = <&i2c_scl &i2c_sda>;
+ };
+ };
+
+ functions {
+ i2c {
+ groups = <&i2c_grp>;
+ };
+ };
+
spi-pins {
function = "spi";
groups = "spi_grp";
--
2.31.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-10 11:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 11:42 [PATCH V3 0/2] dt-bindings: pinctrl: pins, groups & functions Rafał Miłecki
2021-12-10 11:42 ` [PATCH V3 1/2] dt-bindings: pinctrl: support specifying " Rafał Miłecki
2021-12-10 23:26 ` Linus Walleij
2021-12-11 11:16 ` Rafał Miłecki
2021-12-14 19:59 ` Rob Herring
2021-12-14 20:10 ` Rafał Miłecki
2021-12-14 21:50 ` Rafał Miłecki
2021-12-10 11:42 ` Rafał Miłecki [this message]
2021-12-10 14:02 ` [PATCH V3 2/2] dt-bindings: pinctrl: brcm, ns-pinmux: describe " Rob Herring
2021-12-11 7:07 ` [PATCH V3 2/2] dt-bindings: pinctrl: brcm,ns-pinmux: " Tony Lindgren
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=20211210114222.26581-3-zajec5@gmail.com \
--to=zajec5@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).