RE: [PATCH v2] drm/imagination: DRM_POWERVR should depend on ARCH_K3

[Biju Das]

Hi Adam Ford,

> -----Original Message-----
> From: Adam Ford <aford173@xxxxxxxxx>
> Sent: Thursday, February 15, 2024 11:36 PM
> Subject: Re: [PATCH v2] drm/imagination: DRM_POWERVR should depend on
> ARCH_K3
> 
> On Thu, Feb 15, 2024 at 11:22 AM Adam Ford <aford173@xxxxxxxxx> wrote:
> >
> > On Thu, Feb 15, 2024 at 11:10 AM Adam Ford <aford173@xxxxxxxxx> wrote:
> > >
> > > On Thu, Feb 15, 2024 at 10:54 AM Geert Uytterhoeven
> > > <geert@xxxxxxxxxxxxxx> wrote:
> > > >
> > > > Hi Maxime,
> > > >
> > > > On Thu, Feb 15, 2024 at 5:18 PM Maxime Ripard <mripard@xxxxxxxxxx>
> wrote:
> > > > > On Thu, Feb 15, 2024 at 01:50:09PM +0100, Geert Uytterhoeven
> wrote:
> > > > > > Using the Imagination Technologies PowerVR Series 6 GPU
> > > > > > requires a proprietary firmware image, which is currently only
> > > > > > available for Texas Instruments K3 AM62x SoCs.  Hence add a
> > > > > > dependency on ARCH_K3, to prevent asking the user about this
> > > > > > driver when configuring a kernel without Texas Instruments K3
> Multicore SoC support.
> > > > >
> > > > > This wasn't making sense the first time you sent it, and now
> > > > > that commit log is just plain wrong. We have firmwares for the
> > > > > G6110, GX6250, GX6650, BXE-4-32, and BXS-4-64 models, which can
> > > > > be found on (at least) Renesas, Mediatek, Rockchip, TI and
> > > > > StarFive, so across three
> > > >
> > > > I am so happy to be proven wrong!
> > > > Yeah, GX6650 is found on e.g. R-Car H3, and GX6250 on e.g. R-Car M3-
> W.
> > > >
> > > > > architectures and 5 platforms. In two months.
> > > >
> > > > That sounds like great progress, thanks a lot!
> > > >
> > > Geert,
> > >
> > > > Where can I find these firmwares? Linux-firmware[1] seems to lack
> > > > all but the original K3 AM62x one.
> > >
> > > I think PowerVR has a repo [1], but the last time I checked it, the
> > > BVNC for the firmware didn't match what was necessary for the GX6250
> > > on the RZ/G2M.  I can't remember what the corresponding R-Car3 model
> > > is.  I haven't tried recently because I was told more documentation
> > > for firmware porting would be delayed until everything was pushed
> > > into the kernel and Mesa.  Maybe there is a better repo and/or newer
> > > firmware somewhere else.
> > >
> > I should have doubled checked the repo contents before I sent my last
> > e-mail , but it appears the firmware  [2] for the RZ/G2M, might be
> > present now. I don't know if there are driver updates necessary. I
> > checked my e-mails, but I didn't see any notification, or I would have
> > tried it earlier.  Either way, thank you Frank for adding it.  I'll
> > try to test when I have some time.
> >
> 
> I don't have the proper version of Mesa setup yet, but for what it's
> worth, the firmware loads without error, and it doesn't hang.

Based on [1] and [2],

kmscube should work on R-Car as it works on RZ/G2L with panfrost as earlier version of RZ/G2L
which uses drm based on RCar-Du, later changed to rzg2l-du.

[1]
https://elixir.bootlin.com/mesa/mesa-24.0.1/source/src/gallium/targets/dri/meson.build#L95

and 

[2]
https://elixir.bootlin.com/mesa/mesa-24.0.1/source/src/gallium/targets/dri/target.c#L123

Cheers,
Biju

> 
> [    9.787836] powervr fd000000.gpu: [drm] loaded firmware
> powervr/rogue_4.45.2.58_v1.fw
> [    9.787861] powervr fd000000.gpu: [drm] FW version v1.0 (build 6513336
> OS)
> 
>