2022-04-12 23:04:07

by Jayesh Choudhary

[permalink] [raw]
Subject: [PATCH] arm64: dts: ti: k3-am62: Add SA3UL ranges in cbass_main

Add the address space for SA3UL to the ranges property of the
cbass_main node.

Signed-off-by: Jayesh Choudhary <[email protected]>
---
arch/arm64/boot/dts/ti/k3-am62.dtsi | 1 +
1 file changed, 1 insertion(+)

diff --git a/arch/arm64/boot/dts/ti/k3-am62.dtsi b/arch/arm64/boot/dts/ti/k3-am62.dtsi
index bc2997b18556..37fcbe7a3c33 100644
--- a/arch/arm64/boot/dts/ti/k3-am62.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62.dtsi
@@ -66,6 +66,7 @@
<0x00 0x30200000 0x00 0x30200000 0x00 0x00010000>, /* DSS */
<0x00 0x31000000 0x00 0x31000000 0x00 0x00050000>, /* USB0 DWC3 Core window */
<0x00 0x31100000 0x00 0x31100000 0x00 0x00050000>, /* USB1 DWC3 Core window */
+ <0x00 0x40900000 0x00 0x40900000 0x00 0x00030000>, /* SA3UL */
<0x00 0x43600000 0x00 0x43600000 0x00 0x00010000>, /* SA3 sproxy data */
<0x00 0x44043000 0x00 0x44043000 0x00 0x00000fe0>, /* TI SCI DEBUG */
<0x00 0x44860000 0x00 0x44860000 0x00 0x00040000>, /* SA3 sproxy config */
--
2.17.1


2022-04-29 02:25:06

by Bryan Brattlof

[permalink] [raw]
Subject: Re: [PATCH] arm64: dts: ti: k3-am62: Add SA3UL ranges in cbass_main

On April 12, 2022 thus sayeth Jayesh Choudhary:
> Add the address space for SA3UL to the ranges property of the
> cbass_main node.
>
> Signed-off-by: Jayesh Choudhary <[email protected]>

Looks good to me Jayesh!

Reviewed-by: Bryan Brattlof <[email protected]>

~Bryan

2022-05-02 20:22:39

by Vignesh Raghavendra

[permalink] [raw]
Subject: Re: [PATCH] arm64: dts: ti: k3-am62: Add SA3UL ranges in cbass_main

Hi Jayesh Choudhary,

On Tue, 12 Apr 2022 13:20:08 +0530, Jayesh Choudhary wrote:
> Add the address space for SA3UL to the ranges property of the
> cbass_main node.
>
>

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

[1/1] arm64: dts: ti: k3-am62: Add SA3UL ranges in cbass_main
commit: c024c46fe13bb9e9a70d044fd2d63dbee82bbb59

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