linux-kernel - Re: [PATCH RFC v3 2/3] firmware: mediatek: Add vcp ipc protocol interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <d55bcde48451f403172833ecf48fbc9066915e57.camel@mediatek.com>
Date: Wed, 19 Mar 2025 02:45:40 +0000
From: Jjian Zhou (周建) <Jjian.Zhou@...iatek.com>
To: "jassisinghbrar@...il.com" <jassisinghbrar@...il.com>, "robh@...nel.org"
	<robh@...nel.org>, "krzk+dt@...nel.org" <krzk+dt@...nel.org>,
	"matthias.bgg@...il.com" <matthias.bgg@...il.com>, "conor+dt@...nel.org"
	<conor+dt@...nel.org>, "krzk@...nel.org" <krzk@...nel.org>, "AngeloGioacchino
 Del Regno" <angelogioacchino.delregno@...labora.com>
CC: "linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "linux-mediatek@...ts.infradead.org"
	<linux-mediatek@...ts.infradead.org>, "wenst@...omium.org"
	<wenst@...omium.org>, "devicetree@...r.kernel.org"
	<devicetree@...r.kernel.org>, Project_Global_Chrome_Upstream_Group
	<Project_Global_Chrome_Upstream_Group@...iatek.com>
Subject: Re: [PATCH RFC v3 2/3] firmware: mediatek: Add vcp ipc protocol
 interface

On Tue, 2025-03-18 at 10:00 +0100, Krzysztof Kozlowski wrote:
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> 
> 
> On 18/03/2025 09:32, Jjian Zhou (周建) wrote:
> > > > +
> > > > +     return IPI_ACTION_DONE;
> > > > +}
> > > > +EXPORT_SYMBOL(mtk_vcp_ipc_send);
> > > 
> > > Drop export - no users
> > > 
> > > Anyway, every export must be GPL.
> > 
> > The Video Companion Processor (VCP) driver (currently being
> > prepared
> > for submission to the community) will call it.
> > 
> 
> It does not work like that. You must post the users NOW.
> 
> NAK
> 

Let's review this patch together after the VCP driver is ready. Patch 1
and Patch 3 will be combined into v4 for review. How do you think?

> 
> ...
> 
> > > Check goes immediately after declaration. I doubt it is useful in
> > > the
> > > first place as this cannot even happen...
> > > 
> > > 
> > > > +             dev_err(dev, "No platform data available\n");
> > > 
> > > No, drop. Cannot happen or fix your drivers. Who provides the
> > > platdata here?
> > 
> > The VCP driver will call platform_device_register_data to register
> > the
> > structure data. mtk_vcp_ipc_probe will be triggered by vcp_probe.
> > This
> > structure data is the structure we described in the cover letter.
> 
> 
> Comment is still valid.

Let's review this patch together after the VCP driver is ready. Patch 1
and Patch 3 will be combined into v4 for review. How do you think?

> 
> Best regards,
> Krzysztof