[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <168682577717.2266254.12712212456915723597.b4-ty@ti.com>
Date: Thu, 15 Jun 2023 16:13:08 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: <nm@...com>, <kristo@...nel.org>, <conor+dt@...nel.org>,
<robh+dt@...nel.org>, <krzysztof.kozlowski+dt@...aro.org>,
<afd@...com>, Vaishnav Achath <vaishnav.a@...com>
CC: Vignesh Raghavendra <vigneshr@...com>,
<devicetree@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <u-kumar1@...com>
Subject: Re: [PATCH v2 0/4] arm64: dts: ti: j721e: Add HyperFlash support
Hi Vaishnav Achath,
On Sat, 13 May 2023 18:03:09 +0530, Vaishnav Achath wrote:
> This series adds hyperflash support for J721E. J721E SoC has HyperBus
> and OSPI controller muxed within the FSS subsystem and the J721E SoM
> has a 64 MiB S28 OSPI flash and a 64 MiB Hyperflash present which is
> muxed externally also.
>
> Changelog:
> V1->V2:
> * Address feedback in similar series:
> https://lore.kernel.org/all/feddcd03-1848-b667-6a38-ae7c0f6ff160@ti.com/
> * Add partitions information in Hyperflash node.
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/4] arm64: dts: ti: k3-j721e-mcu-wakeup: Add HyperBus node
commit: d93036b47f354b7acb95aad5c91e9becbe4e9f61
[2/4] arm64: dts: ti: k3-j721e-som-p0: Add HyperFlash node
commit: 0979c0069cb669528d13818410de9f0dd41585f3
[3/4] arm64: dts: ti: k3-j7200-common-proc-board: Add OSPI/Hyperflash select pinmux
commit: be8be0d036b2fed1f705931ac3901077039b7496
[4/4] arm64: dts: ti: k3-j721e-common-proc-board: Add OSPI/Hyperflash select pinmux
commit: 58cd171af4d7e27525b1924b72100cba98d88d2a
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
Powered by blists - more mailing lists