mbox series

[v3,0/2] arm64: dts: ti: k3-j784s4-evm: Add support for OSPI and QSPI flashes

Message ID 20230504080305.38986-1-a-nandan@ti.com
Headers
Series arm64: dts: ti: k3-j784s4-evm: Add support for OSPI and QSPI flashes |

Message

Apurva Nandan May 4, 2023, 8:03 a.m. UTC 
  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(+)

Comments

Vignesh Raghavendra June 15, 2023, 10:47 a.m. UTC | #1 
Hi Apurva Nandan,

On Thu, 04 May 2023 13:33:03 +0530, Apurva Nandan wrote:
> 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.
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/2] arm64: dts: ti: k3-j784s4-mcu-wakeup: Add FSS OSPI0 and FSS OSPI1
      commit: 8758109d135401c8afea0d0e3c51e7a52c843b7b
[2/2] arm64: dts: ti: k3-j784s4-evm: Add support for OSPI and QSPI flashes
      commit: 150ce1b10740c10f87e90e485bc279c205e3f731

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh