[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1ce1bcf60d8540f867b800816acecfff610ee948.camel@ndufresne.ca>
Date: Tue, 30 Apr 2024 12:26:58 -0400
From: Nicolas Dufresne <nicolas@...fresne.ca>
To: Jianfeng Liu <liujianfeng1994@...il.com>, linux-media@...r.kernel.org,
linux-rockchip@...ts.infradead.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc: ezequiel@...guardiasur.com.ar, p.zabel@...gutronix.de,
mchehab@...nel.org, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, heiko@...ech.de, sebastian.reichel@...labora.com,
sfr@...b.auug.org.au, sigmaris@...il.com, linkmauve@...kmauve.fr, Conor
Dooley <conor.dooley@...rochip.com>
Subject: Re: [PATCH v7 1/2] dt-bindings: media: rockchip-vpu: Add rk3588
vpu121 compatible string
Sorry,
[...]
> > + - const: rockchip,rk3568-vpu
>
> Sorry to come that late, but I'm noticing a big mistake here. You said you are
> enabling VDPU121, the JPEG decoder. But we don't have a JPEG decoder driver
> mainline, is there some patches missing ?
>
> Nicolas
Ignore this part, just didn't read carefully. This is about getting H264, VP8
and MPEG2 out of these extra cores of course. I still would like to know how we
will express the grouping of these four cores, so a driver can know they are
identical G1 cores and not bound to be time sliced with an H1 core like the
fifth one? I want to see a plan that will work and will not cause headache for
future work on fully utilizing the HW resources.
Nicolas
Powered by blists - more mailing lists