From: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
To: <nicolas.ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<ludovic.desroches@microchip.com>, <robh+dt@kernel.org>,
<lee.jones@linaro.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<UNGLinuxDriver@microchip.com>,
<Kavyasree.Kotagiri@microchip.com>, <Manohar.Puri@microchip.com>
Subject: [PATCH 1/2] mfd: dt-bindings: add bindings for lan966 flexcom shared configurations
Date: Thu, 10 Feb 2022 13:15:45 +0530 [thread overview]
Message-ID: <20220210074546.30669-2-kavyasree.kotagiri@microchip.com> (raw)
In-Reply-To: <20220210074546.30669-1-kavyasree.kotagiri@microchip.com>
This adds LAN966 SoC DT bindings documentation for Flexcom
Shared and chip-select configurations.
Signed-off-by: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
---
.../devicetree/bindings/mfd/atmel-flexcom.txt | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/Documentation/devicetree/bindings/mfd/atmel-flexcom.txt b/Documentation/devicetree/bindings/mfd/atmel-flexcom.txt
index 692300117c64..a76622082228 100644
--- a/Documentation/devicetree/bindings/mfd/atmel-flexcom.txt
+++ b/Documentation/devicetree/bindings/mfd/atmel-flexcom.txt
@@ -18,6 +18,15 @@ Required properties:
- <2> for SPI
- <3> for I2C
+Optional properties:
+- Flexcom shared configurations: Each flexcom of lan966 SoC has 2 chip selects.
+ For each chip select, there is a pin configuration register.
+ The width of the configuration register is 21 because there are 21 shared
+ pins on each of which the chip select can be mapped. Each bit of the
+ configuration register represents a different FLEXCOM_SHARED pin.
+ - lan966x-ss-pin: Should be a flexcom shared pin.
+ - lan966x-cs: Should be chip select 0 or 1.
+
Required child:
A single available child device of type matching the "atmel,flexcom-mode"
property.
@@ -41,6 +50,9 @@ flexcom@f8034000 {
#size-cells = <1>;
ranges = <0x0 0xf8034000 0x800>;
atmel,flexcom-mode = <2>;
+ /* Map chip-select index 0 of the flexcom to FLEXCOM_SHARED 9 */
+ lan966x-ss-pin = <9>;
+ lan966x-cs = <0>;
spi@400 {
compatible = "atmel,at91rm9200-spi";
--
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-02-10 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 7:45 [PATCH 0/2] Add support for LAN966 SoC flexcom shared configurations Kavyasree Kotagiri
2022-02-10 7:45 ` Kavyasree Kotagiri [this message]
2022-02-10 7:56 ` [PATCH 1/2] mfd: dt-bindings: add bindings for lan966 " Tudor.Ambarus
2022-02-10 7:45 ` [PATCH 2/2] mfd: atmel-flexcom: Add support " Kavyasree Kotagiri
2022-02-10 7:59 ` Tudor.Ambarus
2022-02-11 9:30 ` Claudiu.Beznea
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=20220210074546.30669-2-kavyasree.kotagiri@microchip.com \
--to=kavyasree.kotagiri@microchip.com \
--cc=Manohar.Puri@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@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