Hi Manorit Chawdhry,
On Thu, 24 Oct 2024 10:50:57 +0530, Manorit Chawdhry wrote:
> The idea of this series is to add bootph-all and bootph-pre-ram property
> in all the leaf nodes wherever required and cleanup any other places where
> bootph-all/bootph-pre-ram exist in the parent nodes as well since now
> the bootloaders can handle it.
>
>
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[01/12] arm64: dts: ti: k3-j784s4-j742s2-mcu-wakeup: Move bootph from mcu_timer1 to mcu_timer0
commit: 1d381865ad86b05328a3c4d841d2f0d2c07a8b6b
[02/12] arm64: dts: ti: k3-j784s4-j742s2-mcu-wakeup: Remove parent nodes bootph-*
commit: c4fbee5eb6fa5212e9e6285b9116e0e2fae42c52
[03/12] arm64: dts: ti: k3-j784s4: Add bootph-* properties
commit: f54d577df4a06c8e075ba9c1bd8fd6c18167d47e
[04/12] arm64: dts: ti: k3-j721s2: Add bootph-* properties
commit: 83ab86a4412f6143acdf75fd315c196d255a0089
[05/12] arm64: dts: ti: k3-j721e: Add bootph-* properties
commit: dd2c7aeca3ece4ab78a9d87fe2dcce365b5ce87d
[06/12] arm64: dts: ti: k3-j7200: Add bootph-* properties
commit: b903ab269e67ce5788b0b2a39db4bd11fd19359b
[07/12] arm64: dts: ti: k3-j784s4-j742s2-evm-common: Remove parent nodes bootph-*
commit: 49b0b706af963424decf4b6c67b09a83af91a067
[08/12] arm64: dts: ti: k3-j721s2-evm*: Add bootph-* properties
commit: 15a432a4a0d2a6b79fdb798539e6fdbc87ed526c
[09/12] arm64: dts: ti: k3-am68-sk*: Add bootph-* properties
commit: 781cb8f1ad769c7999ef3b35f216ff150130f3ee
[10/12] arm64: dts: ti: k3-j721e-evm*: Add bootph-* properties
commit: fbdb8aa4eab8405c8709aab9e3bba48b5a955cbc
[11/12] arm64: dts: ti: k3-j721e-sk*: Add bootph-* properties
commit: e45355835c40eb96fe92ec98cc9a9e9e60df0845
[12/12] arm64: dts: ti: k3-j7200-evm*: Add bootph-* properties
commit: bdb543b1664bb4a54edf6ab651a36915d037220b
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
