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 2/4] dt-bindings: mfd: atmel,flexcom: Add lan966 compatible string and mux properties
Date: Tue, 3 May 2022 16:25:26 +0530 [thread overview]
Message-ID: <20220503105528.12824-3-kavyasree.kotagiri@microchip.com> (raw)
In-Reply-To: <20220503105528.12824-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>
---
.../devicetree/bindings/mfd/atmel,flexcom.yaml | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/Documentation/devicetree/bindings/mfd/atmel,flexcom.yaml b/Documentation/devicetree/bindings/mfd/atmel,flexcom.yaml
index 62dea9b891d8..3e056857c44a 100644
--- a/Documentation/devicetree/bindings/mfd/atmel,flexcom.yaml
+++ b/Documentation/devicetree/bindings/mfd/atmel,flexcom.yaml
@@ -18,6 +18,7 @@ properties:
compatible:
enum:
- atmel,sama5d2-flexcom
+ - microchip,lan966-flexcom
reg:
minItems: 1
@@ -45,6 +46,19 @@ properties:
$ref: /schemas/types.yaml#/definitions/uint32
enum: [0, 1, 2]
+ # The following optional mux properties are only for lan966 flexcoms
+ mux-controls:
+ minItems: 1
+ description: Phandle to the mux controller to map flexcom chip-select
+ to flexcom shared pin.
+
+ mux-control-names:
+ description: String to label the mux controller.
+ minItems: 1
+ items:
+ - const: cs0
+ - const: cs1
+
required:
- compatible
- reg
@@ -64,5 +78,7 @@ examples:
#size-cells = <1>;
ranges = <0x0 0xf8034000 0x800>;
atmel,flexcom-mode = <2>;
+ mux-controls = <&mux 0>;
+ mux-control-names = "cs0";
};
...
--
2.17.1
next prev parent reply other threads:[~2022-05-03 10:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 10:55 [PATCH 0/4] Add support for lan966 flexcom multiplexer Kavyasree Kotagiri
2022-05-03 10:55 ` [PATCH 1/4] dt-bindings: mfd: atmel,flexcom: Convert to json-schema Kavyasree Kotagiri
2022-05-03 12:34 ` Krzysztof Kozlowski
2022-05-03 22:21 ` Rob Herring
2022-05-03 10:55 ` Kavyasree Kotagiri [this message]
2022-05-03 12:37 ` [PATCH 2/4] dt-bindings: mfd: atmel,flexcom: Add lan966 compatible string and mux properties Krzysztof Kozlowski
2022-05-03 10:55 ` [PATCH 3/4] dt-bindings: mux: Add lan966 flexcom mux controller Kavyasree Kotagiri
2022-05-03 12:42 ` Krzysztof Kozlowski
2022-05-03 10:55 ` [PATCH 4/4] mux: lan966: Add support for " Kavyasree Kotagiri
2022-05-03 12:45 ` Krzysztof Kozlowski
2022-05-09 8:25 ` Kavyasree.Kotagiri
2022-05-03 19:57 ` kernel test robot
2022-05-05 20:26 ` kernel test robot
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=20220503105528.12824-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).