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 2/4] dt-bindings: mfd: atmel,flexcom: Add lan966 compatible string and mux properties
Date: Mon, 9 May 2022 14:19:18 +0530 [thread overview]
Message-ID: <20220509084920.14529-3-kavyasree.kotagiri@microchip.com> (raw)
In-Reply-To: <20220509084920.14529-1-kavyasree.kotagiri@microchip.com>
Add lan966 flexcom compatible string and flexcom mux
device tree properties.
Signed-off-by: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
---
.../bindings/mfd/atmel,flexcom.yaml | 52 ++++++++++++++++++-
1 file changed, 51 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mfd/atmel,flexcom.yaml b/Documentation/devicetree/bindings/mfd/atmel,flexcom.yaml
index 79ec7ebc7055..228c095c84ca 100644
--- a/Documentation/devicetree/bindings/mfd/atmel,flexcom.yaml
+++ b/Documentation/devicetree/bindings/mfd/atmel,flexcom.yaml
@@ -16,7 +16,9 @@ description:
properties:
compatible:
- const: atmel,sama5d2-flexcom
+ enum:
+ - atmel,sama5d2-flexcom
+ - microchip,lan966-flexcom
reg:
maxItems: 1
@@ -57,6 +59,27 @@ required:
additionalProperties: false
+allOf:
+ - if:
+ properties:
+ compatible:
+ contains:
+ const: microchip,lan966-flexcom
+
+ then:
+ properties:
+ mux-controls:
+ minItems: 1
+ maxItems: 2
+ $ref: /schemas/types.yaml#/definitions/phandle-array
+
+ mux-control-names:
+ minItems: 1
+ $ref: ../mux/mux-consumer.yaml
+ items:
+ - const: cs0
+ - const: cs1
+
patternProperties:
"^serial@[0-9a-f]+$":
description: See atmel-usart.txt for details of USART bindings.
@@ -89,4 +112,31 @@ examples:
atmel,fifo-size = <32>;
};
};
+
+ - |
+ flx3: flexcom@e0064000 {
+ compatible = "microchip,lan966-flexcom";
+ reg = <0xe0064000 0x100>;
+ clocks = <&fabric_clk>;
+ #address-cells = <1>;
+ #size-cells = <1>;
+ ranges = <0x0 0xe0064000 0x800>;
+ atmel,flexcom-mode = <2>;
+ mux-controls = <&mux 0>;
+ mux-control-names = "cs0";
+
+ spi3: spi@400 {
+ compatible = "atmel,at91rm9200-spi";
+ reg = <0x400 0x200>;
+ interrupts = <0 51 4>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ clocks = <&fabric_clk>;
+ clock-names = "spi_clk";
+ pinctrl-0 = <&fc3_b_sck_pins>, <&fc3_b_rxd_pins>,
+ <&fc3_b_txd_pins>, <&fc_shrd9_pins>;
+ pinctrl-names = "default";
+ atmel,fifo-size = <32>;
+ };
+ };
...
--
2.17.1
next prev parent reply other threads:[~2022-05-09 9:12 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 ` Krzysztof Kozlowski
2022-05-09 8:49 ` Kavyasree Kotagiri [this message]
2022-05-10 10:33 ` [PATCH v2 2/4] dt-bindings: mfd: atmel,flexcom: Add lan966 compatible string and mux properties Krzysztof Kozlowski
2022-05-09 8:49 ` [PATCH v2 3/4] dt-bindings: mux: Add lan966 flexcom mux controller Kavyasree Kotagiri
2022-05-10 10:37 ` 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-3-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).