From: "Jjian Zhou (周建)" <Jjian.Zhou@mediatek.com>
To: "jassisinghbrar@gmail.com" <jassisinghbrar@gmail.com>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"krzk@kernel.org" <krzk@kernel.org>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"wenst@chromium.org" <wenst@chromium.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH RFC v3 2/3] firmware: mediatek: Add vcp ipc protocol interface
Date: Wed, 19 Mar 2025 02:45:40 +0000 [thread overview]
Message-ID: <d55bcde48451f403172833ecf48fbc9066915e57.camel@mediatek.com> (raw)
In-Reply-To: <12f5049d-02e1-4c80-9289-b2dfb1e136a8@kernel.org>
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
next prev parent reply other threads:[~2025-03-19 2:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 11:03 [PATCH RFC v3 0/3] add VCP mailbox and IPC driver Jjian Zhou
2025-03-17 11:03 ` [PATCH RFC v3 1/3] mailbox: mediatek: Add mtk-vcp-mailbox driver Jjian Zhou
2025-03-17 17:15 ` Krzysztof Kozlowski
2025-03-17 11:03 ` [PATCH RFC v3 2/3] firmware: mediatek: Add vcp ipc protocol interface Jjian Zhou
2025-03-17 17:16 ` Krzysztof Kozlowski
2025-03-18 8:32 ` Jjian Zhou (周建)
2025-03-18 9:00 ` Krzysztof Kozlowski
2025-03-19 2:45 ` Jjian Zhou (周建) [this message]
2025-03-17 11:03 ` [PATCH RFC v3 3/3] dt-bindings: mailbox: mtk,mt8196-vcp-mbox: add mtk vcp-mbox document Jjian Zhou
2025-03-17 16:33 ` Rob Herring
2025-03-18 5:54 ` Jjian Zhou (周建)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d55bcde48451f403172833ecf48fbc9066915e57.camel@mediatek.com \
--to=jjian.zhou@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=wenst@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®