Re: [PATCH V8 0/4] arm64: dts: ti: k3-am62{a,p}x-sk: add opp frequencies

[Vignesh Raghavendra]

Hi Dhruva Gole,

On Tue, 08 Oct 2024 18:50:49 +0530, Dhruva Gole wrote:
> This series adds in the OPPs for the Cortex-A53s on the AM62Ax and
> AM62Px SoC families along with the defining the
> WKUP_MMR0_WKUP0_CTRL_MMR0_JTAG_USER_ID which we can use to to properly
> limit the OPPs available for that variant.
> 
> Signed-off-by: Bryan Brattlof <bb@xxxxxx>
> Signed-off-by: Dhruva Gole <d-gole@xxxxxx>
> 
> [...]

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

[1/4] arm64: dts: ti: k3-am62a: add opp frequencies
      commit: aeedca40159c7017f3f0cfbd1ac2066e091e784c
[2/4] arm64: dts: ti: k3-am62a7-sk: add 1.4ghz opp entry
      commit: 5dae00dfaf8e4a40c68c8a4d9e453cd06bc5bf19
[3/4] arm64: dts: ti: k3-am62p: add opp frequencies
      commit: 76d855f0580148d8f07f1c0aa96f33cad382e6cc
[4/4] arm64: dts: ti: k3-am62p5-sk: add 1.4ghz opp entry
      commit: 50f5ad2cb52f322d472dfb451881bea7d7d78d32

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