Re: [PATCH v6 01/14] media: mediatek: vcodec: support vcp architecture

Nicolas Dufresne <[email protected]>
Newsgroups org.infradead.lists.linux-mediatek,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel,org.kernel.vger.linux-media
Organization Collabora Canada
Message-ID <[email protected]>
Le vendredi 14 août 2026 à 02:38 +0000, Kyrie Wu (吴晗) a écrit :
> On Tue, 2026-08-11 at 16:22 -0400, Nicolas Dufresne wrote:
> > Hi Kyrie,
> > 
> > Le lundi 10 août 2026 à 03:05 +0000, Kyrie Wu (吴晗) a écrit :
> > > I agree. Since the platform data is introduced in the MT8189 patch
> > > series, I will move fw_type to the platform data and make
> > > mtk_vcodec_dec_get_chip_name() derive the chip identifier from it
> > > in
> > > the MT8189 series.
> > 
> > I'm not sure I have captured the plan correctly. Would you mind
> > clarifying ?
> > 
> > Nicolas
> 
> Hi Nicolas,
> 
> Sorry, my previous reply was unclear.
> 
> The platform-data refactoring will be included in the next revision of
> the MT8189 series. That series depends on the updated MT8196 encoder
> series, so I need to wait for the new MT8196 encoder revision to be
> posted before I can rebase and send the updated MT8189 series.
> 
> In the updated MT8189 series, `fw_type` and the chip identifier will be
> set in the platform data for each compatible, rather than being derived
> by probing DT properties. Consequently, the DT-property-based selection
> shown in this patch will be removed.
> 
> I will make this dependency explicit in the cover letter. Sorry again
> for not explaining the plan clearly.

Thanks, this will be helpful to handle follow-up series.

Nicolas

> 
> Best regards,
> Kyrie
signature.asc (application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQTvDVKBFcTDwhoEbxLZQZRRKWBy9AUCan8myQAKCRDZQZRRKWBy
9AjrAP47W1O0MlybGV5nddQLSeB987/IQrb90AsBaMHCuSPMNwEAqHnDqWue4hCg
bIF5omk88zNifV9lAU/7JgU1KPCuiAU=
=bcq9
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.