From: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
To: <krzysztof.kozlowski+dt@linaro.org>,
<nicolas.ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<claudiu.beznea@microchip.com>, <peda@axentia.se>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <lee.jones@linaro.org>,
<linux@armlinux.org.uk>, <Manohar.Puri@microchip.com>,
<Kavyasree.Kotagiri@microchip.com>,
<UNGLinuxDriver@microchip.com>
Subject: [PATCH v2 3/4] dt-bindings: mux: Add lan966 flexcom mux controller
Date: Mon, 9 May 2022 14:19:19 +0530 [thread overview]
Message-ID: <20220509084920.14529-4-kavyasree.kotagiri@microchip.com> (raw)
In-Reply-To: <20220509084920.14529-1-kavyasree.kotagiri@microchip.com>
This adds DT bindings documentation for lan966 flexcom
mux controller.
Signed-off-by: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
---
.../mux/microchip,lan966-flx-mux.yaml | 51 +++++++++++++++++++
1 file changed, 51 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mux/microchip,lan966-flx-mux.yaml
diff --git a/Documentation/devicetree/bindings/mux/microchip,lan966-flx-mux.yaml b/Documentation/devicetree/bindings/mux/microchip,lan966-flx-mux.yaml
new file mode 100644
index 000000000000..63147a2e8f3a
--- /dev/null
+++ b/Documentation/devicetree/bindings/mux/microchip,lan966-flx-mux.yaml
@@ -0,0 +1,51 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/mux/microchip,lan966-flx-mux.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Microchip Lan966 Flexcom multiplexer bindings
+
+maintainers:
+ - Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
+
+description: |+
+ The Microchip Lan966 have 5 Flexcoms. Each flexcom has 2 chip-selects
+ when operating in USART and SPI modes.
+ Each chip select of each flexcom can be mapped to 21 flexcom shared pins.
+ Define register offset and pin number to map a flexcom chip-select
+ to flexcom shared pin.
+
+allOf:
+ - $ref: /schemas/mux/mux-controller.yaml#
+
+properties:
+ compatible:
+ const: microchip,lan966-flx-mux
+
+ reg:
+ maxItems: 1
+
+ '#mux-control-cells':
+ const: 1
+
+ mux-offset-pin:
+ description: an array of register offset and flexcom shared pin(0-20).
+
+required:
+ - compatible
+ - reg
+ - '#mux-control-cells'
+ - mux-offset-pin
+
+additionalProperties: false
+
+examples:
+ - |
+ mux: mux-controller@e2004168 {
+ compatible = "microchip,lan966-flx-mux";
+ reg = <0xe2004168 0x8>;
+ #mux-control-cells = <1>;
+ mux-offset-pin = <0x18 9>; /* 0: flx3 cs0 offset, pin-9 */
+ };
+...
--
2.17.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:[~2022-05-09 8:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 8:49 [PATCH v2 0/4] Add support for lan966 flexcom multiplexer Kavyasree Kotagiri
2022-05-09 8:49 ` [PATCH v2 1/4] dt-bindings: mfd: atmel, flexcom: Convert to json-schema Kavyasree Kotagiri
2022-05-10 10:32 ` [PATCH v2 1/4] dt-bindings: mfd: atmel,flexcom: " Krzysztof Kozlowski
2022-05-09 8:49 ` [PATCH v2 2/4] dt-bindings: mfd: atmel, flexcom: Add lan966 compatible string and mux properties Kavyasree Kotagiri
2022-05-10 10:33 ` [PATCH v2 2/4] dt-bindings: mfd: atmel,flexcom: " Krzysztof Kozlowski
2022-05-09 8:49 ` Kavyasree Kotagiri [this message]
2022-05-10 10:37 ` [PATCH v2 3/4] dt-bindings: mux: Add lan966 flexcom mux controller Krzysztof Kozlowski
2022-05-09 8:49 ` [PATCH v2 4/4] mux: lan966: Add support for " Kavyasree Kotagiri
2022-05-09 11:37 ` Peter Rosin
2022-05-09 11:41 ` Peter Rosin
2022-05-10 14:59 ` Kavyasree.Kotagiri
2022-05-10 19:38 ` Peter Rosin
2022-05-11 14:28 ` Kavyasree.Kotagiri
2022-05-11 15:43 ` Peter Rosin
2022-05-27 6:00 ` Kavyasree.Kotagiri
2022-05-17 11:53 ` Michael Walle
2022-05-17 12:00 ` Peter Rosin
2022-05-10 1:46 ` kernel test robot
2022-05-10 3:28 ` kernel test robot
2022-05-11 9:06 ` Claudiu.Beznea
2022-05-23 14:52 ` Lee Jones
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=20220509084920.14529-4-kavyasree.kotagiri@microchip.com \
--to=kavyasree.kotagiri@microchip.com \
--cc=Manohar.Puri@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nicolas.ferre@microchip.com \
--cc=peda@axentia.se \
/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).