From: Vaishnav Achath <vaishnav.a@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<j-keerthy@ti.com>, <u-kumar1@ti.com>, <vaishnav.a@ti.com>
Subject: [PATCH 0/8] arm64: dts: ti: j7: Add device-tree nodes for MCSPI
Date: Mon, 20 Mar 2023 11:00:14 +0530 [thread overview]
Message-ID: <20230320053022.11093-1-vaishnav.a@ti.com> (raw)
This series adds device tree nodes for Multi Channel Serial Peripheral
Interface (MCSPI) on J721E, J7200, J721S2 and J784S4 platforms. All the
MCSPI instances are disabled by default and can be enabled through overlays
as required, the changes were tested using spidev loopback test for all
instances and the data verified only for main_spi4 which is connected
internally as slave to mcu_spi2 for all existing J7 devices.
Vaishnav Achath (8):
arm64: dts: ti: k3-j721e-main: Add MCSPI nodes
arm64: dts: ti: k3-j721e-mcu-wakeup: Add MCSPI nodes
arm64: dts: ti: k3-j7200-main: Add MCSPI nodes
arm64: dts: ti: k3-j7200-mcu-wakeup: Add MCSPI nodes
arm64: dts: ti: k3-j721s2-main: Add MCSPI nodes
arm64: dts: ti: k3-j721s2-mcu-wakeup: Add MCSPI nodes
arm64: dts: ti: k3-j784s4-main: Add MCSPI nodes
arm64: dts: ti: k3-j784s4-mcu-wakeup: Add MCSPI nodes
arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 88 +++++++++++++++++++
.../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 33 +++++++
arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 88 +++++++++++++++++++
.../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 33 +++++++
arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 88 +++++++++++++++++++
.../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 33 +++++++
arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi | 88 +++++++++++++++++++
.../boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 33 +++++++
8 files changed, 484 insertions(+)
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-03-20 5:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 5:30 Vaishnav Achath [this message]
2023-03-20 5:30 ` [PATCH 1/8] arm64: dts: ti: k3-j721e-main: Add MCSPI nodes Vaishnav Achath
2023-03-20 5:30 ` [PATCH 2/8] arm64: dts: ti: k3-j721e-mcu-wakeup: " Vaishnav Achath
2023-03-20 5:30 ` [PATCH 3/8] arm64: dts: ti: k3-j7200-main: " Vaishnav Achath
2023-03-20 5:30 ` [PATCH 4/8] arm64: dts: ti: k3-j7200-mcu-wakeup: " Vaishnav Achath
2023-03-20 5:30 ` [PATCH 5/8] arm64: dts: ti: k3-j721s2-main: " Vaishnav Achath
2023-03-20 5:30 ` [PATCH 6/8] arm64: dts: ti: k3-j721s2-mcu-wakeup: " Vaishnav Achath
2023-03-20 5:30 ` [PATCH 7/8] arm64: dts: ti: k3-j784s4-main: " Vaishnav Achath
2023-03-20 5:30 ` [PATCH 8/8] arm64: dts: ti: k3-j784s4-mcu-wakeup: " Vaishnav Achath
2023-03-20 15:16 ` [PATCH 0/8] arm64: dts: ti: j7: Add device-tree nodes for MCSPI Nishanth Menon
2023-03-21 6:59 ` Vaishnav Achath
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=20230320053022.11093-1-vaishnav.a@ti.com \
--to=vaishnav.a@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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