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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <DC1HS8D8KLIF.2MN7D9EXGQQ45@ti.com>
Date: Wed, 13 Aug 2025 12:56:22 -0500
From: Randolph Sapp <rs@...com>
To: Nishanth Menon <nm@...com>
CC: <vigneshr@...com>, <kristo@...nel.org>, <robh@...nel.org>,
        <krzk+dt@...nel.org>, <conor+dt@...nel.org>, <d-gole@...com>,
        <afd@...com>, <bb@...com>, <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <detheridge@...com>, <matt.coster@...tec.com>,
        Michael Walle
	<mwalle@...nel.org>
Subject: Re: [PATCH 2/3] arm64: dts: ti: k3-am62p-j722s: enable the bxs-4-64

On Wed Aug 13, 2025 at 10:17 AM CDT, Nishanth Menon wrote:
> On 18:25-20250808, rs@...com wrote:
>> From: Randolph Sapp <rs@...com>
>> 
>> 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.
>> 
>> Signed-off-by: Randolph Sapp <rs@...com>
>> ---
>>  .../boot/dts/ti/k3-am62p-j722s-common-main.dtsi     | 13 +++++++++++++
>>  1 file changed, 13 insertions(+)
>> 
>> diff --git a/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi
>> index 2e5e25a8ca86..a51db8f9dff8 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi
>> @@ -690,6 +690,19 @@ ospi0: spi@...0000 {
>>  		};
>>  	};
>>  
>> +	gpu: gpu@...0000 {
>> +		compatible = "ti,j721s2-gpu", "img,img-bxs-4-64", "img,img-rogue";
>
> Note the discussion in https://lore.kernel.org/linux-arm-kernel/DBE4UO2RGAYX.17V1DAF8MQYJM@kernel.org/
>
>> +		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@...0000 {
>>  		compatible = "ti,am642-cpsw-nuss";
>>  		#address-cells = <2>;
>> -- 
>> 2.50.1
>> 
>
> Is the issue that Michael reported
> https://lore.kernel.org/linux-arm-kernel/20250716134717.4085567-3-mwalle@kernel.org/
> 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.