From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 05888CA0EE9 for ; Mon, 18 Aug 2025 21:27:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:References:To: From:Subject:CC:Message-ID:Date:Content-Type:Content-Transfer-Encoding: MIME-Version:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=hbqjR77flrEojaMmvXfL0GY1fNUeEb1Qsxjgnrp8ask=; b=V8bU42Bf27zOpeT520xCjlu0IU K+VC8rB7hyKrDRkwtO+83Vcbw9WbiVvtZfG86/YGYWt8WBKMm+A/ZQ32VeMGy+7JipVisXGuoaEnK mDHl54JpB0xjoDnqMHYLe6NxXyDa/lGN0uL2w1gAVu649nA8auf4vt6LJEjEvRUu9XuqnW9fPAGOp IJIB2+8Fh4hbQkDN5zSMvWdm17niwVrlRKEfpBpbraAsKmzgPCxbYHVwaVdlGC0g1wGf3v+SpEjuD weA5UeISoUSF4F6zdC2SsA8ch87otikOrwJ0e45BqMe8Gnvh/bjqcL5O0niCHAMODkG7cTF/vmB4i 9y5KAe3Q==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1uo7O2-00000008iAI-4BRz; Mon, 18 Aug 2025 21:27:27 +0000 Received: from fllvem-ot03.ext.ti.com ([198.47.19.245]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1uo5ll-00000008YII-44tz for linux-arm-kernel@lists.infradead.org; Mon, 18 Aug 2025 19:43:51 +0000 Received: from lelvem-sh02.itg.ti.com ([10.180.78.226]) by fllvem-ot03.ext.ti.com (8.15.2/8.15.2) with ESMTP id 57IJhhNE2728942; Mon, 18 Aug 2025 14:43:43 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1755546223; bh=hbqjR77flrEojaMmvXfL0GY1fNUeEb1Qsxjgnrp8ask=; h=Date:CC:Subject:From:To:References:In-Reply-To; b=Jw77B70ciHlBfvOueY2p0pueCXi8VH5bRDrpHynFr5WH4FN0I6fdE/Lqen5rkZg+q mtDvWjWje+lLMMgM50BIw2TX4jn7cAFep+BoOMy6vUioZzjU6tmwAvyXGFq/PWAUxb bX+18JRiHEAcJwvPBkfur+0WN9Rc4LpZJWLr3ck4= Received: from DFLE113.ent.ti.com (dfle113.ent.ti.com [10.64.6.34]) by lelvem-sh02.itg.ti.com (8.18.1/8.18.1) with ESMTPS id 57IJhhcg515659 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA256 bits=128 verify=FAIL); Mon, 18 Aug 2025 14:43:43 -0500 Received: from DFLE105.ent.ti.com (10.64.6.26) by DFLE113.ent.ti.com (10.64.6.34) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.55; Mon, 18 Aug 2025 14:43:42 -0500 Received: from lelvem-mr05.itg.ti.com (10.180.75.9) by DFLE105.ent.ti.com (10.64.6.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.55 via Frontend Transport; Mon, 18 Aug 2025 14:43:42 -0500 Received: from localhost (rs-desk.dhcp.ti.com [128.247.81.144]) by lelvem-mr05.itg.ti.com (8.18.1/8.18.1) with ESMTP id 57IJhgLn1830747; Mon, 18 Aug 2025 14:43:42 -0500 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Date: Mon, 18 Aug 2025 14:43:42 -0500 Message-ID: CC: , , , , , , , , , , , , Subject: Re: [PATCH 3/3] arm64: dts: ti: k3-j784s4-j742s2: enable the bxs-4-64 From: Randolph Sapp To: Michael Walle , Nishanth Menon X-Mailer: aerc 0.20.1-0-g2ecb8770224a-dirty References: <20250808232522.1296240-1-rs@ti.com> <20250808232522.1296240-3-rs@ti.com> <20250813151819.5rthljjrpryfwezz@skinning> <20250813181300.xfpsu23arx7xy4fy@anointer> In-Reply-To: X-C2ProcessedOrg: 333ef613-75bf-4e12-a4b1-8e3623f5dcea X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20250818_124350_100467_73D2BE91 X-CRM114-Status: GOOD ( 23.04 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon Aug 18, 2025 at 1:22 AM CDT, Michael Walle wrote: > Hi, > > On Wed Aug 13, 2025 at 8:13 PM CEST, Nishanth Menon wrote: >> On 12:58-20250813, Randolph Sapp wrote: >> > On Wed Aug 13, 2025 at 10:18 AM CDT, Nishanth Menon wrote: >> > > On 18:25-20250808, rs@ti.com wrote: >> > >> From: Randolph Sapp >> > >>=20 >> > >> Add the relevant device tree node for Imagination's BXS-4-64 GPU. >> > >>=20 >> > >> These devices uses a similar MSMC configuration to the J721S2. As s= uch, >> > >> they also require the use of the dma-coherent attribute. >> > >>=20 >> > >> Signed-off-by: Randolph Sapp >> > >> --- >> > >> .../boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi | 14 ++++++++++= ++++ >> > >> 1 file changed, 14 insertions(+) >> > >>=20 >> > >> diff --git a/arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dt= si b/arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi >> > >> index 7c5b0c69897d..a44ca34dda62 100644 >> > >> --- a/arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi >> > >> +++ b/arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi >> > >> @@ -2691,4 +2691,18 @@ bist_main14: bist@33c0000 { >> > >> bootph-pre-ram; >> > >> ti,sci-dev-id =3D <234>; >> > >> }; >> > >> + >> > >> + gpu: gpu@4e20000000 { >> > >> + compatible =3D "ti,j721s2-gpu", "img,img-bxs-4-64", "img,img-rog= ue"; >> > > >> > > Following https://lore.kernel.org/linux-arm-kernel/DBE4UO2RGAYX.17V= 1DAF8MQYJM@kernel.org/ >> > > Is it worth having ti,j784s4-gpu here? Are there any SoC specific qu= irks >> > > that driver will need to handle? >> >=20 >> > 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. >> >=20 >> >> 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 Ah, I don't see that series on the linux-arm-kernel list. If you can forwar= d me that I can work around whatever you've got.