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

Message

Dhruva Gole Oct. 8, 2024, 1:20 p.m. UTC

Hello everyone

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 <[e-mail]>
Signed-off-by: Dhruva Gole <[e-mail]>

Changelog:
---

Changes in v8:
- Split the driver fixes out and sent a separate series for that.
- This series is now the same as it was in v3. Just rebased on 6.12-rc1
- Link to v7: https://lore.kernel.org/all/[e-mail]/

Changes in v7:
- Based on Andrew's comments, re-worded the comment in the driver and also
  used a different approach for finding old DT, this way it's less error prone
  than how things were done in v6.
- Added a warning print when using old DT:
https://gist.github.com/DhruvaG2000/63f5e28636d52787488f776e5bf39498#file-am62x-cpufreq-test-log-old-dt-txt-L220
- Link to v6: https://lore.kernel.org/r/[e-mail]

Changes in v6:
- Ensure backward compaibility for AM625 DT, by handling the old DT in a special
way inside the cpufreq driver itself. This is based on feedback from Nishanth
where we are not okay to break the old DT working with new kernels.
- Link to v5: https://lore.kernel.org/r/[e-mail]

Changes in v5:
- Based on Andrew's review on v4 of "arm64: dts: ti: k3-am62: use opp_efuse_table for opp-table syscon",
	- s/syscon@43000000/bus@43000000/
	- Drop the "reg = <>;" line
- Link to v4: https://lore.kernel.org/all/[e-mail]/

Changes in v4:
- Add 2 more patches to this series:
	- Driver cleanup as described above.
	- AM625 DT fixups (Link to v1 of that patch: https://lore.kernel.org/all/[e-mail]/)
- Link to v3: https://lore.kernel.org/all/[e-mail]/

Changes in v3:
- Miscellaneous spelling fixes in commit body
- Link to v2: https://lore.kernel.org/r/[e-mail]

Changes in v2:
- Expanded on commit descriptions
- Split board file and SoC fdt changes into different patches
- Link to v1: https://lore.kernel.org/r/[e-mail]

---

Bryan Brattlof (4):
  arm64: dts: ti: k3-am62a: add opp frequencies
  arm64: dts: ti: k3-am62a7-sk: add 1.4ghz opp entry
  arm64: dts: ti: k3-am62p: add opp frequencies
  arm64: dts: ti: k3-am62p5-sk: add 1.4ghz opp entry

 arch/arm64/boot/dts/ti/k3-am62a-wakeup.dtsi   |  5 ++
 arch/arm64/boot/dts/ti/k3-am62a7-sk.dts       |  9 ++++
 arch/arm64/boot/dts/ti/k3-am62a7.dtsi         | 51 +++++++++++++++++++
 .../dts/ti/k3-am62p-j722s-common-wakeup.dtsi  |  5 ++
 arch/arm64/boot/dts/ti/k3-am62p5-sk.dts       |  9 ++++
 arch/arm64/boot/dts/ti/k3-am62p5.dtsi         | 47 +++++++++++++++++
 6 files changed, 126 insertions(+)


base-commit: 33ce24234fca4c083e6685a18b460a18ebb5d5c1

Comments

Vignesh Raghavendra Nov. 5, 2024, 9:14 a.m. UTC | #1

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 <[e-mail]>
> Signed-off-by: Dhruva Gole <[e-mail]>
> 
> [...]

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