linux-kernel - Re: [PATCH 0/3] arm64: dts: ti: Add bootph-all tags for PCIe boot support on J784S4 SoC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <176266923841.19596.4147637793586614093.b4-ty@ti.com>
Date: Sun, 9 Nov 2025 11:52:28 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: <nm@...com>, <kristo@...nel.org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
	<conor+dt@...nel.org>, Hrushikesh Salunke <h-salunke@...com>
CC: Vignesh Raghavendra <vigneshr@...com>, <s-vadapalli@...com>,
	<danishanwar@...com>, <linux-arm-kernel@...ts.infradead.org>,
	<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] arm64: dts: ti: Add bootph-all tags for PCIe boot support on J784S4 SoC

Hi Hrushikesh Salunke,

On Fri, 17 Oct 2025 14:16:51 +0530, Hrushikesh Salunke wrote:
> J784S4 SoC uses its PCIe1 instance as part of the PCIe boot process. This
> series adds the necessary "bootph-all" boot phase tags to all the device tree
> nodes that need to be functional at all stages of the PCIe boot process.
> 
> This series is based on commit
> 13863a59e410 (tag: next-20251014) Add linux-next specific files for 20251014
> 
> [...]

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

[1/3] arm64: dts: ti: k3-j784s4-evm-pcie0-pcie1-ep: Add boot phase tag to "pcie1_ep"
      commit: 1f03b9e71e49a2f903c914f12ca5068995d916d7
[2/3] arm64: dts: ti: k3-j784s4-j742s2-evm-common: Add bootph-all tag to SERDES0
      commit: cadd9234aedc9d4c5b4342f96a1ebe02314adeb2
[3/3] arm64: dts: ti: k3-j784s4-j742s2-evm-common: Add bootph-all tag to "pcie1_ctrl"
      commit: 56bf2702cab02d6781c6201fc407be356bb256fd

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