From: Randolph Sapp <rs@ti.com>
To: Michael Walle <michael@walle.cc>, Nishanth Menon <nm@ti.com>
Cc: <vigneshr@ti.com>, <kristo@kernel.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>, <d-gole@ti.com>,
<afd@ti.com>, <bb@ti.com>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<detheridge@ti.com>, <matt.coster@imgtec.com>
Subject: Re: [PATCH 3/3] arm64: dts: ti: k3-j784s4-j742s2: enable the bxs-4-64
Date: Mon, 18 Aug 2025 14:43:42 -0500 [thread overview]
Message-ID: <DC5T752T3P8B.1UC57G2GH35Z5@ti.com> (raw)
In-Reply-To: <DC5C5JA237HD.1ACBQVG1LYQ7Z@walle.cc>
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 <rs@ti.com>
>> > >>
>> > >> 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.
>> > >>
>> > >> Signed-off-by: Randolph Sapp <rs@ti.com>
>> > >> ---
>> > >> .../boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi | 14 ++++++++++++++
>> > >> 1 file changed, 14 insertions(+)
>> > >>
>> > >> diff --git a/arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi 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 = <234>;
>> > >> };
>> > >> +
>> > >> + gpu: gpu@4e20000000 {
>> > >> + compatible = "ti,j721s2-gpu", "img,img-bxs-4-64", "img,img-rogue";
>> > >
>> > > Following https://lore.kernel.org/linux-arm-kernel/DBE4UO2RGAYX.17V1DAF8MQYJM@kernel.org/
>> > > 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.
>> >
>>
>> 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 forward me
that I can work around whatever you've got.
next prev parent reply other threads:[~2025-08-18 19:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 23:25 [PATCH 1/3] arm64: dts: ti: k3-am62p: Fix memory ranges for GPU rs
2025-08-08 23:25 ` [PATCH 2/3] arm64: dts: ti: k3-am62p-j722s: enable the bxs-4-64 rs
2025-08-13 15:17 ` Nishanth Menon
2025-08-13 17:56 ` Randolph Sapp
2025-08-13 18:10 ` Nishanth Menon
2025-08-13 18:42 ` Nishanth Menon
2025-08-14 20:40 ` Randolph Sapp
2025-08-15 1:16 ` Nishanth Menon
2025-08-08 23:25 ` [PATCH 3/3] arm64: dts: ti: k3-j784s4-j742s2: " rs
2025-08-13 15:18 ` Nishanth Menon
2025-08-13 17:58 ` Randolph Sapp
2025-08-13 18:13 ` Nishanth Menon
2025-08-18 6:22 ` Michael Walle
2025-08-18 19:43 ` Randolph Sapp [this message]
2025-08-19 6:38 ` Michael Walle
2025-08-19 20:47 ` Randolph Sapp
2025-08-21 11:33 ` Nishanth Menon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DC5T752T3P8B.1UC57G2GH35Z5@ti.com \
--to=rs@ti.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=detheridge@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.coster@imgtec.com \
--cc=michael@walle.cc \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®