Received-SPF: pass (google.com: domain of linux-kernel+bounces-68725-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Date: Fri, 16 Feb 2024 15:14:08 +0100
From: Maxime Ripard <mripard@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Adam Ford <aford173@gmail.com>, 
	Geert Uytterhoeven <geert@linux-m68k.org>, Frank Binns <frank.binns@imgtec.com>, 
	Matt Coster <matt.coster@imgtec.com>, Maarten Lankhorst <maarten.lankhorst@linux.intel.com>, 
	Thomas Zimmermann <tzimmermann@suse.de>, David Airlie <airlied@gmail.com>, 
	Daniel Vetter <daniel@ffwll.ch>, Sarah Walker <sarah.walker@imgtec.com>, 
	"dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, 
	Javier Martinez Canillas <javierm@redhat.com>, Nishanth Menon <nm@ti.com>, 
	Marek Vasut <marek.vasut@mailbox.org>, Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: RE: RE: [PATCH v2] drm/imagination: DRM_POWERVR should depend on
 ARCH_K3
Message-ID: <wxwad77x2mxhhwdsbgiytzn6x54t4sywodjhzefwldo277njiz@ru7z54wxgelu>
References: <6be2558b8462fc08095c24c9257563ab5f3ae013.1708001398.git.geert+renesas@glider.be>
 <kycepdxukfsww3tnxoo5hoiuo3vcgpqqmynokzhtl4vodgm6zc@ih4uhw7gz4jh>
 <CAMuHMdVf7ophCwKt-n_N-LBHV4+t14Gjb4d1O0T8FDk_9xMFtA@mail.gmail.com>
 <CAHCN7xJ65RP8TO7cS0p5DwE6zru5NEF0_JA+8siT_OpSeLD7pA@mail.gmail.com>
 <CAHCN7x+EnSU8qk5dBFco=0vkeknGq18qEN7vFmZs0_q83T_3+w@mail.gmail.com>
 <CAHCN7xKffJ29zyjoJVAcy3b_d=-zkFzbL=URj4yWJWzYvRdB_Q@mail.gmail.com>
 <TYCPR01MB11269CBE8429A31DE5002A5A5864C2@TYCPR01MB11269.jpnprd01.prod.outlook.com>
 <nzrkujogauvn262ucxippwidyub6ikcohcjpbpn4hzj7rymctm@4owntgrmcquf>
 <TYCPR01MB11269CBAA20275E11D9AD6500864C2@TYCPR01MB11269.jpnprd01.prod.outlook.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="v6zk4jxmpuh5uajd"
Content-Disposition: inline
In-Reply-To: <TYCPR01MB11269CBAA20275E11D9AD6500864C2@TYCPR01MB11269.jpnprd01.prod.outlook.com>


--v6zk4jxmpuh5uajd
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 16, 2024 at 09:13:14AM +0000, Biju Das wrote:
> Hi Maxime Ripard,
>=20
> > -----Original Message-----
> > From: Maxime Ripard <mripard@kernel.org>
> > Sent: Friday, February 16, 2024 9:05 AM
> > Subject: Re: RE: [PATCH v2] drm/imagination: DRM_POWERVR should depend =
on
> > ARCH_K3
> >=20
> > On Fri, Feb 16, 2024 at 08:47:46AM +0000, Biju Das wrote:
> > > Hi Adam Ford,
> > >
> > > > -----Original Message-----
> > > > From: Adam Ford <aford173@gmail.com>
> > > > 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=E2=80=AFAM Adam Ford <aford173@gmail.=
com> wrote:
> > > > >
> > > > > On Thu, Feb 15, 2024 at 11:10=E2=80=AFAM Adam Ford <aford173@gmai=
l.com>
> > wrote:
> > > > > >
> > > > > > On Thu, Feb 15, 2024 at 10:54=E2=80=AFAM Geert Uytterhoeven
> > > > > > <geert@linux-m68k.org> wrote:
> > > > > > >
> > > > > > > Hi Maxime,
> > > > > > >
> > > > > > > On Thu, Feb 15, 2024 at 5:18=E2=80=AFPM Maxime Ripard
> > > > > > > <mripard@kernel.org>
> > > > 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 el=
se.
> > > > > >
> > > > > 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 chan=
ged
> > to rzg2l-du.
> >=20
> > IIRC, the mesa support isn't there yet for kmscube to start.
>=20
> What about glmark2? I tested glmark2 as well.

It's not really a matter of kmscube itself, but the interaction with the
compositor entirely. You can run a headless vulkan rendering, but an
application that renders to a window won't work.

Maxime

--v6zk4jxmpuh5uajd
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCZc9tsAAKCRDj7w1vZxhR
xcnGAQD5CBylgkDZNdCl/pKDpsaGrLRJbCmkrP4nBuIIyATfgQD7BuOie/iGRBWI
hBlixgDo5tqqY/4QNJmZ88R6yPkUyg8=
=cjDh
-----END PGP SIGNATURE-----

--v6zk4jxmpuh5uajd--