From: Apurva Nandan <a-nandan@ti.com>
To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Apurva Nandan <a-nandan@ti.com>, Dhruva Gole <d-gole@ti.com>,
Udit Kumar <u-kumar1@ti.com>, Vaishnav Achath <vaishnav.a@ti.com>
Subject: [PATCH v3 0/2] arm64: dts: ti: k3-j784s4-evm: Add support for OSPI and QSPI flashes
Date: Thu, 4 May 2023 13:33:03 +0530 [thread overview]
Message-ID: <20230504080305.38986-1-a-nandan@ti.com> (raw)
From: Vaishnav Achath <vaishnav.a@ti.com>
J784S4 has S28HS512T OSPI flash connected to OSPI0 and MT25QU512A QSPI
flash connected to OSPI1, enable support for the same.
Changes in v3:
- Split the SoC dtsi changes and EVM dts changes into separate patches
- Added QSPI flash node and partition information in EVM dts
- Removed address-cells = <1>; and size-cells = <1>; in OSPI0 flash node
- Add flash partition information for OSPI flash.
Changes in v2:
- Fixed address 0x0 to 0x00
- Fixed dtbs_check errors (removed syscon and created simple bus)
- Fixed whitespace error
Apurva Nandan (2):
arm64: dts: ti: k3-j784s4-mcu-wakeup: Add FSS OSPI0 and FSS OSPI1
arm64: dts: ti: k3-j784s4-evm: Add support for OSPI and QSPI flashes
arch/arm64/boot/dts/ti/k3-j784s4-evm.dts | 158 ++++++++++++++++++
.../boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 41 +++++
2 files changed, 199 insertions(+)
--
2.17.1
next reply other threads:[~2023-05-04 8:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 8:03 Apurva Nandan [this message]
2023-05-04 8:03 ` [PATCH v3 1/2] arm64: dts: ti: k3-j784s4-mcu-wakeup: Add FSS OSPI0 and FSS OSPI1 Apurva Nandan
2023-05-04 8:03 ` [PATCH v3 2/2] arm64: dts: ti: k3-j784s4-evm: Add support for OSPI and QSPI flashes Apurva Nandan
2023-05-04 8:10 ` [PATCH v3 0/2] " Apurva Nandan
2023-06-15 10:47 ` Vignesh Raghavendra
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=20230504080305.38986-1-a-nandan@ti.com \
--to=a-nandan@ti.com \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--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®