From: "J, KEERTHY" <j-keerthy@ti.com>
To: Vaishnav Achath <vaishnav.a@ti.com>, <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>,
<u-kumar1@ti.com>, <j-luthra@ti.com>
Subject: Re: [PATCH v2 0/4] arm64: dts: ti: j7: Add device-tree nodes for MCSPI
Date: Tue, 21 Mar 2023 13:02:55 +0530 [thread overview]
Message-ID: <b651a7f5-3d61-fe8b-13b0-7f0caf0f21fd@ti.com> (raw)
In-Reply-To: <20230321065447.6997-1-vaishnav.a@ti.com>
On 3/21/2023 12:24 PM, Vaishnav Achath wrote:
> 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.
>
> V1->V2:
> * Address Nishanth's feedback, combine main, mcu domain
> MCSPI node addition changes to single commit per SoC.
Vaishnav,
As per TRM "MCSPI4 is directly connected as a slave to MCU_MCSPI2 by
default at power-up. MCSPI4 and MCU_MCSPI2 are not pinned out externally".
The above is applicable to J721e/J7200. Similar mapping might be
existing for j721s2 & j784s4 as well. Add this information in
the commit log. Other than that For the series:
Reviewed-by: Keerthy <j-keerthy@ti.com>
Regards,
Keerthy
>
> Vaishnav Achath (4):
> arm64: dts: ti: k3-j721e: Add MCSPI nodes
> arm64: dts: ti: k3-j7200: Add MCSPI nodes
> arm64: dts: ti: k3-j721s2: Add MCSPI nodes
> arm64: dts: ti: k3-j784s4: 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(+)
>
prev parent reply other threads:[~2023-03-21 7:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 6:54 Vaishnav Achath
2023-03-21 6:54 ` [PATCH v2 1/4] arm64: dts: ti: k3-j721e: Add MCSPI nodes Vaishnav Achath
2023-03-21 6:54 ` [PATCH v2 2/4] arm64: dts: ti: k3-j7200: " Vaishnav Achath
2023-03-21 6:54 ` [PATCH v2 3/4] arm64: dts: ti: k3-j721s2: " Vaishnav Achath
2023-03-21 6:54 ` [PATCH v2 4/4] arm64: dts: ti: k3-j784s4: " Vaishnav Achath
2023-03-21 7:32 ` J, KEERTHY [this message]
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=b651a7f5-3d61-fe8b-13b0-7f0caf0f21fd@ti.com \
--to=j-keerthy@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=j-luthra@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=vaishnav.a@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
all inboxes | Powered by JetHome®