Skip to contentSkip to conversation

arm64: dts: ti: k3-am62p: Fix memory ranges for GPU

PATCH In review [email protected] 3 participants 17 messages Aug 8, 2025 – Aug 21, 2025

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/3 arm64: dts: ti: k3-am62p: Fix memory ranges for GPU

From: Randolph Sapp <[email protected]>

Update the memory region listed in the k3-am62p.dtsi for the BXS-4-64 GPU to match the Main Memory Map described in the TRM [1].

[1] https://www.ti.com/lit/ug/spruj83b/spruj83b.pdf

Fixes 29075cc09f43 ("arm64: dts: ti: Introduce AM62P5 family of SoCs")
---
 arch/arm64/boot/dts/ti/k3-am62p.dtsi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/boot/dts/ti/k3-am62p.dtsi +1 -1
index 75a15c368c11..dd24c40c7965 100644
@@ -59,7 +59,7 @@ cbass_main: bus@f0000 {
 			 <0x00 0x01000000 0x00 0x01000000 0x00 0x01b28400>, /* First peripheral window */
 			 <0x00 0x08000000 0x00 0x08000000 0x00 0x00200000>, /* Main CPSW */
 			 <0x00 0x0e000000 0x00 0x0e000000 0x00 0x01d20000>, /* Second peripheral window */
-			 <0x00 0x0fd00000 0x00 0x0fd00000 0x00 0x00020000>, /* GPU */
+			 <0x00 0x0fd80000 0x00 0x0fd80000 0x00 0x00080000>, /* GPU */
 			 <0x00 0x20000000 0x00 0x20000000 0x00 0x0a008000>, /* Third peripheral window */
 			 <0x00 0x30040000 0x00 0x30040000 0x00 0x00080000>, /* PRUSS-M */
 			 <0x00 0x30101000 0x00 0x30101000 0x00 0x00010100>, /* CSI window */
Signature · 1 line
2.50.1
#1 lore raw

PATCH 2/3 arm64: dts: ti: k3-am62p-j722s: enable the bxs-4-64

From: Randolph Sapp <[email protected]>

Add the relevant device tree node for Imagination's BXS-4-64 GPU.

These devices specifically do not set the dma-coherent bit because they do not use the same MSMC configuration as other BXS-4-64 enabled TI platforms.

---
 .../boot/dts/ti/k3-am62p-j722s-common-main.dtsi     | 13 +++++++++++++
 1 file changed, 13 insertions(+)
arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi +13 -0
index 2e5e25a8ca86..a51db8f9dff8 100644
@@ -690,6 +690,19 @@ ospi0: spi@fc40000 {
 		};
 	};
 
+	gpu: gpu@fd80000 {
+		compatible = "ti,j721s2-gpu", "img,img-bxs-4-64", "img,img-rogue";
+		reg = <0x00 0x0fd80000 0x00 0x80000>;
+		clocks = <&k3_clks 237 1>;
+		clock-names = "core";
+		assigned-clocks = <&k3_clks 237 1>;
+		assigned-clock-rates = <800000000>;
+		interrupts = <GIC_SPI 241 IRQ_TYPE_LEVEL_HIGH>;
+		power-domains = <&k3_pds 237 TI_SCI_PD_EXCLUSIVE>,
+				<&k3_pds 242 TI_SCI_PD_EXCLUSIVE>;
+		power-domain-names = "a", "b";
+	};
+
 	cpsw3g: ethernet@8000000 {
 		compatible = "ti,am642-cpsw-nuss";
 		#address-cells = <2>;
Signature · 1 line
2.50.1
maintainer
#2 lore raw

Re: [PATCH 2/3] arm64: dts: ti: k3-am62p-j722s: enable the bxs-4-64

Quoted 18 lines · On 18:25-20250808, [email protected] wrote:

From: Randolph Sapp <[email protected]>

Add the relevant device tree node for Imagination's BXS-4-64 GPU.

These devices specifically do not set the dma-coherent bit because they do not use the same MSMC configuration as other BXS-4-64 enabled TI platforms.

---
 .../boot/dts/ti/k3-am62p-j722s-common-main.dtsi     | 13 +++++++++++++
 1 file changed, 13 insertions(+)
arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi +0 -0
index 2e5e25a8ca86..a51db8f9dff8 100644

arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi ospi0: spi@fc40000 { · line 694

Quoted 5 lines
arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi +2 -0
@@ -690,6 +690,19 @@ ospi0: spi@fc40000 {
 		};
 	};
 
+	gpu: gpu@fd80000 {
+		compatible = "ti,j721s2-gpu", "img,img-bxs-4-64", "img,img-rogue";

Note the discussion in https://lore.kernel.org/linux-arm-kernel/[email protected]/

Quoted 17 lines
arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi +11 -0
+		reg = <0x00 0x0fd80000 0x00 0x80000>;
+		clocks = <&k3_clks 237 1>;
+		clock-names = "core";
+		assigned-clocks = <&k3_clks 237 1>;
+		assigned-clock-rates = <800000000>;
+		interrupts = <GIC_SPI 241 IRQ_TYPE_LEVEL_HIGH>;
+		power-domains = <&k3_pds 237 TI_SCI_PD_EXCLUSIVE>,
+				<&k3_pds 242 TI_SCI_PD_EXCLUSIVE>;
+		power-domain-names = "a", "b";
+	};
+
 	cpsw3g: ethernet@8000000 {
 		compatible = "ti,am642-cpsw-nuss";
 		#address-cells = <2>;
Signature · 1 line
2.50.1

Is the issue that Michael reported
https://lore.kernel.org/linux-arm-kernel/[email protected]/
resolved?

Signature · 4 lines
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
https://ti.com/opensource
#3 lore raw

Re: [PATCH 2/3] arm64: dts: ti: k3-am62p-j722s: enable the bxs-4-64

Quoted 40 lines · Nishanth Menon
Quoted 18 lines · On 18:25-20250808, [email protected] wrote:

From: Randolph Sapp <[email protected]>

Add the relevant device tree node for Imagination's BXS-4-64 GPU.

These devices specifically do not set the dma-coherent bit because they do not use the same MSMC configuration as other BXS-4-64 enabled TI platforms.

---
 .../boot/dts/ti/k3-am62p-j722s-common-main.dtsi     | 13 +++++++++++++
 1 file changed, 13 insertions(+)
arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi +0 -0
index 2e5e25a8ca86..a51db8f9dff8 100644

arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi ospi0: spi@fc40000 { · line 694

Quoted 5 lines
arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi +2 -0
@@ -690,6 +690,19 @@ ospi0: spi@fc40000 {
 		};
 	};
 
+	gpu: gpu@fd80000 {
+		compatible = "ti,j721s2-gpu", "img,img-bxs-4-64", "img,img-rogue";

Note the discussion in https://lore.kernel.org/linux-arm-kernel/[email protected]/

Quoted 13 lines
arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi +11 -0
+		reg = <0x00 0x0fd80000 0x00 0x80000>;
+		clocks = <&k3_clks 237 1>;
+		clock-names = "core";
+		assigned-clocks = <&k3_clks 237 1>;
+		assigned-clock-rates = <800000000>;
+		interrupts = <GIC_SPI 241 IRQ_TYPE_LEVEL_HIGH>;
+		power-domains = <&k3_pds 237 TI_SCI_PD_EXCLUSIVE>,
+				<&k3_pds 242 TI_SCI_PD_EXCLUSIVE>;
+		power-domain-names = "a", "b";
+	};
+
 	cpsw3g: ethernet@8000000 {
 		compatible = "ti,am642-cpsw-nuss";
Quoted 8 lines
Quoted 4 lines
arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi +0 -0
 		#address-cells = <2>;
Signature · 1 line
2.50.1

Is the issue that Michael reported
https://lore.kernel.org/linux-arm-kernel/[email protected]/
resolved?

Define resolved. If by resolved you mean using the same hack we have had on the out of tree module for years, then yes it is resolved.

maintainer
#4 lore raw

Re: [PATCH 2/3] arm64: dts: ti: k3-am62p-j722s: enable the bxs-4-64

Quoted 50 lines · Randolph Sapp
Quoted 40 lines · Nishanth Menon
Quoted 18 lines · On 18:25-20250808, [email protected] wrote:

From: Randolph Sapp <[email protected]>

Add the relevant device tree node for Imagination's BXS-4-64 GPU.

These devices specifically do not set the dma-coherent bit because they do not use the same MSMC configuration as other BXS-4-64 enabled TI platforms.

---
 .../boot/dts/ti/k3-am62p-j722s-common-main.dtsi     | 13 +++++++++++++
 1 file changed, 13 insertions(+)
arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi +0 -0
index 2e5e25a8ca86..a51db8f9dff8 100644

arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi ospi0: spi@fc40000 { · line 694

Quoted 5 lines
arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi +2 -0
@@ -690,6 +690,19 @@ ospi0: spi@fc40000 {
 		};
 	};
 
+	gpu: gpu@fd80000 {
+		compatible = "ti,j721s2-gpu", "img,img-bxs-4-64", "img,img-rogue";

Note the discussion in https://lore.kernel.org/linux-arm-kernel/[email protected]/

Quoted 13 lines
arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi +11 -0
+		reg = <0x00 0x0fd80000 0x00 0x80000>;
+		clocks = <&k3_clks 237 1>;
+		clock-names = "core";
+		assigned-clocks = <&k3_clks 237 1>;
+		assigned-clock-rates = <800000000>;
+		interrupts = <GIC_SPI 241 IRQ_TYPE_LEVEL_HIGH>;
+		power-domains = <&k3_pds 237 TI_SCI_PD_EXCLUSIVE>,
+				<&k3_pds 242 TI_SCI_PD_EXCLUSIVE>;
+		power-domain-names = "a", "b";
+	};
+
 	cpsw3g: ethernet@8000000 {
 		compatible = "ti,am642-cpsw-nuss";
Quoted 8 lines
Quoted 4 lines
arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi +0 -0
 		#address-cells = <2>;
Signature · 1 line
2.50.1

Is the issue that Michael reported
https://lore.kernel.org/linux-arm-kernel/[email protected]/
resolved?

Quoted 2 lines

Define resolved. If by resolved you mean using the same hack we have had on the out of tree module for years, then yes it is resolved.

Please share a bootlog with gpu and linux-next kernel with just this series applied? Please provide complete lsmod and cat /proc/interrupts for reference.

Signature · 4 lines
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
https://ti.com/opensource
maintainer
#5 lore raw

Re: [PATCH 2/3] arm64: dts: ti: k3-am62p-j722s: enable the bxs-4-64

In reply to Randolph Sapp

On 12:56-20250813, Randolph Sapp wrote:
[...]

Quoted 5 lines
Quoted 5 lines

arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi ospi0: spi@fc40000 { · line 699

Quoted 5 lines
arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi +5 -0
+		reg = <0x00 0x0fd80000 0x00 0x80000>;
+		clocks = <&k3_clks 237 1>;
+		clock-names = "core";
+		assigned-clocks = <&k3_clks 237 1>;
+		assigned-clock-rates = <800000000>;

btw, as per https://www.ti.com/lit/ds/symlink/tda4aen-q1.pdf (page 86) 720MHz when vdd_core is 0.75v (default)
and 800MHz when vdd_core is 0.85v

0.85v is set in the board dts and higher OPPs are enabled depending on board capability.

You might want to check the assigned-clock-rates based on data sheet, default should'nt need a assigned-clock-rate.

Signature · 4 lines
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
https://ti.com/opensource
#6 lore raw

Re: [PATCH 2/3] arm64: dts: ti: k3-am62p-j722s: enable the bxs-4-64

Quoted 13 lines · Nishanth Menon

On 12:56-20250813, Randolph Sapp wrote:
[...]

Quoted 5 lines
Quoted 5 lines

arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi ospi0: spi@fc40000 { · line 699

Quoted 5 lines
arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi +5 -0
+		reg = <0x00 0x0fd80000 0x00 0x80000>;
+		clocks = <&k3_clks 237 1>;
+		clock-names = "core";
+		assigned-clocks = <&k3_clks 237 1>;
+		assigned-clock-rates = <800000000>;

btw, as per https://www.ti.com/lit/ds/symlink/tda4aen-q1.pdf (page 86) 720MHz when vdd_core is 0.75v (default)
and 800MHz when vdd_core is 0.85v

Quoted 5 lines

0.85v is set in the board dts and higher OPPs are enabled depending on board capability.

You might want to check the assigned-clock-rates based on data sheet, default should'nt need a assigned-clock-rate.

Are you suggesting that we set assigned-clock-rates in the board dts instead, or do you just want to do away with assigned-clock-rates in general and eat the perf difference?

maintainer
#7 lore raw

Re: [PATCH 2/3] arm64: dts: ti: k3-am62p-j722s: enable the bxs-4-64

Quoted 17 lines · Randolph Sapp
Quoted 16 lines · Nishanth Menon

On 12:56-20250813, Randolph Sapp wrote:
[...]

Quoted 5 lines
Quoted 5 lines

arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi ospi0: spi@fc40000 { · line 699

Quoted 5 lines
arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi +5 -0
+		reg = <0x00 0x0fd80000 0x00 0x80000>;
+		clocks = <&k3_clks 237 1>;
+		clock-names = "core";
+		assigned-clocks = <&k3_clks 237 1>;
+		assigned-clock-rates = <800000000>;

btw, as per https://www.ti.com/lit/ds/symlink/tda4aen-q1.pdf (page 86) 720MHz when vdd_core is 0.75v (default)
and 800MHz when vdd_core is 0.85v

0.85v is set in the board dts and higher OPPs are enabled depending on board capability.

Quoted 6 lines
Quoted 2 lines

You might want to check the assigned-clock-rates based on data sheet, default should'nt need a assigned-clock-rate.

Are you suggesting that we set assigned-clock-rates in the board dts instead, or do you just want to do away with assigned-clock-rates in general and eat the perf difference?

The higher frequency is possible unless you know that the board is setup for the higher voltage. So, set it board device tree file.

Look at what we did with OPP-High support on AM625 for example. That frequency can only be reliably achieved if vdd_core is 0.85v. And base SoC dtsi must assume safe default (min voltage of 0.75v) as the node is enabled by default.

Signature · 4 lines
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
https://ti.com/opensource
#8 lore raw

PATCH 3/3 arm64: dts: ti: k3-j784s4-j742s2: enable the bxs-4-64

In reply to [email protected]

From: Randolph Sapp <[email protected]>

Add the relevant device tree node for Imagination's BXS-4-64 GPU.

These devices uses a similar MSMC configuration to the J721S2. As such, they also require the use of the dma-coherent attribute.

---
 .../boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi  | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi +14 -0
index 7c5b0c69897d..a44ca34dda62 100644
@@ -2691,4 +2691,18 @@ bist_main14: bist@33c0000 {
 		bootph-pre-ram;
 		ti,sci-dev-id = <234>;
 	};
+
+	gpu: gpu@4e20000000 {
+		compatible = "ti,j721s2-gpu", "img,img-bxs-4-64", "img,img-rogue";
+		reg = <0x4e 0x20000000 0x00 0x80000>;
+		clocks = <&k3_clks 181 1>;
+		clock-names = "core";
+		assigned-clocks = <&k3_clks 181 1>;
+		assigned-clock-rates = <800000000>;
+		interrupts = <GIC_SPI 24 IRQ_TYPE_LEVEL_HIGH>;
+		power-domains = <&k3_pds 181 TI_SCI_PD_EXCLUSIVE>,
+				<&k3_pds 182 TI_SCI_PD_EXCLUSIVE>;
+		power-domain-names = "a", "b";
+		dma-coherent;
+	};
 };
Signature · 1 line
2.50.1
maintainer
#9 lore raw

Re: [PATCH 3/3] arm64: dts: ti: k3-j784s4-j742s2: enable the bxs-4-64

Quoted 17 lines · On 18:25-20250808, [email protected] wrote:

From: Randolph Sapp <[email protected]>

Add the relevant device tree node for Imagination's BXS-4-64 GPU.

These devices uses a similar MSMC configuration to the J721S2. As such, they also require the use of the dma-coherent attribute.

---
 .../boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi  | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi +0 -0
index 7c5b0c69897d..a44ca34dda62 100644

arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi bist_main14: bist@33c0000 { · line 2696

Quoted 6 lines
arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi +3 -0
@@ -2691,4 +2691,18 @@ bist_main14: bist@33c0000 {
 		bootph-pre-ram;
 		ti,sci-dev-id = <234>;
 	};
+
+	gpu: gpu@4e20000000 {
+		compatible = "ti,j721s2-gpu", "img,img-bxs-4-64", "img,img-rogue";

Following https://lore.kernel.org/linux-arm-kernel/[email protected]/
Is it worth having ti,j784s4-gpu here? Are there any SoC specific quirks that driver will need to handle?

Quoted 15 lines
arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi +11 -0
+		reg = <0x4e 0x20000000 0x00 0x80000>;
+		clocks = <&k3_clks 181 1>;
+		clock-names = "core";
+		assigned-clocks = <&k3_clks 181 1>;
+		assigned-clock-rates = <800000000>;
+		interrupts = <GIC_SPI 24 IRQ_TYPE_LEVEL_HIGH>;
+		power-domains = <&k3_pds 181 TI_SCI_PD_EXCLUSIVE>,
+				<&k3_pds 182 TI_SCI_PD_EXCLUSIVE>;
+		power-domain-names = "a", "b";
+		dma-coherent;
+	};
 };
Signature · 1 line
2.50.1
Signature · 4 lines
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
https://ti.com/opensource
#10 lore raw

Re: [PATCH 3/3] arm64: dts: ti: k3-j784s4-j742s2: enable the bxs-4-64

Quoted 13 lines · Nishanth Menon
Quoted 12 lines · On 18:25-20250808, [email protected] wrote:

From: Randolph Sapp <[email protected]>

Add the relevant device tree node for Imagination's BXS-4-64 GPU.

These devices uses a similar MSMC configuration to the J721S2. As such, they also require the use of the dma-coherent attribute.

---
 .../boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi  | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
Quoted 15 lines

arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi bist_main14: bist@33c0000 { · line 2696

Quoted 11 lines
arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi +3 -0
index 7c5b0c69897d..a44ca34dda62 100644
@@ -2691,4 +2691,18 @@ bist_main14: bist@33c0000 {
 		bootph-pre-ram;
 		ti,sci-dev-id = <234>;
 	};
+
+	gpu: gpu@4e20000000 {
+		compatible = "ti,j721s2-gpu", "img,img-bxs-4-64", "img,img-rogue";

Following https://lore.kernel.org/linux-arm-kernel/[email protected]/
Is it worth having ti,j784s4-gpu here? Are there any SoC specific quirks that driver will need to handle?

No SoC specific quirks, aside from those already being tracked through the dma-coherent attribute. If we actually want to register SoC specific compatibility entries as advised by the kernel docs, just let me know. I've seen this opinion toggle a few times.

Quoted 15 lines
Quoted 15 lines
arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi +11 -0
+		reg = <0x4e 0x20000000 0x00 0x80000>;
+		clocks = <&k3_clks 181 1>;
+		clock-names = "core";
+		assigned-clocks = <&k3_clks 181 1>;
+		assigned-clock-rates = <800000000>;
+		interrupts = <GIC_SPI 24 IRQ_TYPE_LEVEL_HIGH>;
+		power-domains = <&k3_pds 181 TI_SCI_PD_EXCLUSIVE>,
+				<&k3_pds 182 TI_SCI_PD_EXCLUSIVE>;
+		power-domain-names = "a", "b";
+		dma-coherent;
+	};
 };
Signature · 1 line
2.50.1
maintainer
#11 lore raw

Re: [PATCH 3/3] arm64: dts: ti: k3-j784s4-j742s2: enable the bxs-4-64

Quoted 30 lines · Randolph Sapp
Quoted 13 lines · Nishanth Menon
Quoted 12 lines · On 18:25-20250808, [email protected] wrote:

From: Randolph Sapp <[email protected]>

Add the relevant device tree node for Imagination's BXS-4-64 GPU.

These devices uses a similar MSMC configuration to the J721S2. As such, they also require the use of the dma-coherent attribute.

---
 .../boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi  | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
Quoted 15 lines

arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi bist_main14: bist@33c0000 { · line 2696

Quoted 11 lines
arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi +3 -0
index 7c5b0c69897d..a44ca34dda62 100644
@@ -2691,4 +2691,18 @@ bist_main14: bist@33c0000 {
 		bootph-pre-ram;
 		ti,sci-dev-id = <234>;
 	};
+
+	gpu: gpu@4e20000000 {
+		compatible = "ti,j721s2-gpu", "img,img-bxs-4-64", "img,img-rogue";

Following https://lore.kernel.org/linux-arm-kernel/[email protected]/
Is it worth having ti,j784s4-gpu here? Are there any SoC specific quirks that driver will need to handle?

Quoted 5 lines

No SoC specific quirks, aside from those already being tracked through the dma-coherent attribute. If we actually want to register SoC specific compatibility entries as advised by the kernel docs, just let me know. I've seen this opinion toggle a few times.

Please provide bootlogs on linux-next with just this series applied. IMHO, based on what I see at the moment on GPU, it might be a good idea to have SoC specific compatibility entries.

Signature · 4 lines
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
https://ti.com/opensource
#12 lore raw

Re: [PATCH 3/3] arm64: dts: ti: k3-j784s4-j742s2: enable the bxs-4-64

Hi,

Quoted 37 lines · Nishanth Menon
Quoted 30 lines · Randolph Sapp
Quoted 13 lines · Nishanth Menon
Quoted 12 lines · On 18:25-20250808, [email protected] wrote:

From: Randolph Sapp <[email protected]>

Add the relevant device tree node for Imagination's BXS-4-64 GPU.

These devices uses a similar MSMC configuration to the J721S2. As such, they also require the use of the dma-coherent attribute.

---
 .../boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi  | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
Quoted 15 lines

arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi bist_main14: bist@33c0000 { · line 2696

Quoted 11 lines
arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi +3 -0
index 7c5b0c69897d..a44ca34dda62 100644
@@ -2691,4 +2691,18 @@ bist_main14: bist@33c0000 {
 		bootph-pre-ram;
 		ti,sci-dev-id = <234>;
 	};
+
+	gpu: gpu@4e20000000 {
+		compatible = "ti,j721s2-gpu", "img,img-bxs-4-64", "img,img-rogue";

Following https://lore.kernel.org/linux-arm-kernel/[email protected]/
Is it worth having ti,j784s4-gpu here? Are there any SoC specific quirks that driver will need to handle?

Quoted 5 lines

No SoC specific quirks, aside from those already being tracked through the dma-coherent attribute. If we actually want to register SoC specific compatibility entries as advised by the kernel docs, just let me know. I've seen this opinion toggle a few times.

Quoted 3 lines

Please provide bootlogs on linux-next with just this series applied. IMHO, based on what I see at the moment on GPU, it might be a good idea to have SoC specific compatibility entries.

IMHO, that's *always* a good idea, even if the IP is the very same as the integration might be different.

Apart from that, we now have two series which partly overlap. Should I repost mine, as that's more than just the DT entry? (Which doesn't work as is, I'd guess.)

-michael

#13 lore raw

Re: [PATCH 3/3] arm64: dts: ti: k3-j784s4-j742s2: enable the bxs-4-64

Quoted 44 lines · Michael Walle

Hi,

Quoted 37 lines · Nishanth Menon
Quoted 30 lines · Randolph Sapp
Quoted 13 lines · Nishanth Menon
Quoted 12 lines · On 18:25-20250808, [email protected] wrote:

From: Randolph Sapp <[email protected]>

Add the relevant device tree node for Imagination's BXS-4-64 GPU.

These devices uses a similar MSMC configuration to the J721S2. As such, they also require the use of the dma-coherent attribute.

---
 .../boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi  | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
Quoted 15 lines

arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi bist_main14: bist@33c0000 { · line 2696

Quoted 11 lines
arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi +3 -0
index 7c5b0c69897d..a44ca34dda62 100644
@@ -2691,4 +2691,18 @@ bist_main14: bist@33c0000 {
 		bootph-pre-ram;
 		ti,sci-dev-id = <234>;
 	};
+
+	gpu: gpu@4e20000000 {
+		compatible = "ti,j721s2-gpu", "img,img-bxs-4-64", "img,img-rogue";

Following https://lore.kernel.org/linux-arm-kernel/[email protected]/
Is it worth having ti,j784s4-gpu here? Are there any SoC specific quirks that driver will need to handle?

Quoted 5 lines

No SoC specific quirks, aside from those already being tracked through the dma-coherent attribute. If we actually want to register SoC specific compatibility entries as advised by the kernel docs, just let me know. I've seen this opinion toggle a few times.

Quoted 3 lines

Please provide bootlogs on linux-next with just this series applied. IMHO, based on what I see at the moment on GPU, it might be a good idea to have SoC specific compatibility entries.

Quoted 8 lines

IMHO, that's *always* a good idea, even if the IP is the very same as the integration might be different.

Apart from that, we now have two series which partly overlap. Should I repost mine, as that's more than just the DT entry? (Which doesn't work as is, I'd guess.)

-michael

Ah, I don't see that series on the linux-arm-kernel list. If you can forward me that I can work around whatever you've got.

#14 lore raw

Re: [PATCH 3/3] arm64: dts: ti: k3-j784s4-j742s2: enable the bxs-4-64

Hi,

Quoted 6 lines
Quoted 3 lines

Apart from that, we now have two series which partly overlap. Should I repost mine, as that's more than just the DT entry? (Which doesn't work as is, I'd guess.)

Ah, I don't see that series on the linux-arm-kernel list. If you can forward me that I can work around whatever you've got.

That was the one Nishanth mentioned earlier:
https://lore.kernel.org/linux-arm-kernel/[email protected]/

Also this:
https://lore.kernel.org/all/[email protected]/

-michael

#15 lore raw

Re: [PATCH 3/3] arm64: dts: ti: k3-j784s4-j742s2: enable the bxs-4-64

Quoted 10 lines · Michael Walle

Hi,

Quoted 7 lines
Quoted 3 lines

Apart from that, we now have two series which partly overlap. Should I repost mine, as that's more than just the DT entry? (Which doesn't work as is, I'd guess.)

Ah, I don't see that series on the linux-arm-kernel list. If you can forward me
that I can work around whatever you've got.

Quoted 7 lines

That was the one Nishanth mentioned earlier:
https://lore.kernel.org/linux-arm-kernel/[email protected]/

Also this:
https://lore.kernel.org/all/[email protected]/

-michael

Ah, alright. I'll hold off on this series until the AM62P related sections you were proposing are picked up.

maintainer
#16 lore raw

Re: [PATCH 3/3] arm64: dts: ti: k3-j784s4-j742s2: enable the bxs-4-64

Quoted 14 lines · Randolph Sapp
Quoted 13 lines · Michael Walle

Hi,

Quoted 7 lines
Quoted 3 lines

Apart from that, we now have two series which partly overlap. Should I repost mine, as that's more than just the DT entry? (Which doesn't work as is, I'd guess.)

Ah, I don't see that series on the linux-arm-kernel list. If you can forward me
that I can work around whatever you've got.

That was the one Nishanth mentioned earlier:
https://lore.kernel.org/linux-arm-kernel/[email protected]/

Quoted 7 lines
Quoted 4 lines

Also this:
https://lore.kernel.org/all/[email protected]/

-michael

Ah, alright. I'll hold off on this series until the AM62P related sections you were proposing are picked up.

Are all SoCs impacted by this need? just hold off the am62p changes, perhaps?

Signature · 4 lines
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
https://ti.com/opensource