From: moudy.ho <moudy.ho@mediatek.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Rob Landley <rob@landley.net>, <linux-media@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
Alexandre Courbot <acourbot@chromium.org>, <tfiga@chromium.org>,
<drinkcat@chromium.org>, <pihsun@chromium.org>,
<hsinyi@google.com>,
Benjamin Gaignard <benjamin.gaignard@collabora.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
daoyuan huang <daoyuan.huang@mediatek.com>,
Ping-Hsun Wu <ping-hsun.wu@mediatek.com>,
<allen-kh.cheng@mediatek.com>, <xiandong.wang@mediatek.com>,
<randy.wu@mediatek.com>, <jason-jh.lin@mediatek.com>,
<roy-cw.yeh@mediatek.com>, <river.cheng@mediatek.com>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
<cellopoint.kai@gmail.com>
Subject: Re: [DKIM] [PATCH v21 4/4] media: platform: mtk-mdp3: add Mediatek MDP3 driver
Date: Mon, 11 Jul 2022 16:25:58 +0800 [thread overview]
Message-ID: <5e3aa17cad22fc8f321fbcc3159ac510f34dc3ea.camel@mediatek.com> (raw)
In-Reply-To: <Ysfo1h75vAIUjcmB@pendragon.ideasonboard.com>
On Fri, 2022-07-08 at 11:20 +0300, Laurent Pinchart wrote:
> On Fri, Jul 08, 2022 at 10:08:44AM +0200, Hans Verkuil wrote:
> > Hi Moudy,
> >
> > Some comments below:
>
> And one more
>
> > On 7/6/22 09:54, Moudy Ho wrote:
> > > This patch adds driver for Mediatek's Media Data Path ver.3
> > > (MDP3).
> > > It provides the following functions:
> > > color transform, format conversion, resize, crop, rotate, flip
> > > and additional image quality enhancement.
> > >
> > > The MDP3 driver is mainly used for Google Chromebook products to
> > > import the new architecture to set the HW settings as shown
> > > below:
> > > User -> V4L2 framework
> > > -> MDP3 driver -> SCP (setting calculations)
> > > -> MDP3 driver -> CMDQ (GCE driver) -> HW
> > >
> > > Each modules' related operation control is sited in mtk-mdp3-
> > > comp.c
> > > Each modules' register table is defined in file with "mdp_reg_"
> > > prefix
> > > GCE related API, operation control sited in mtk-mdp3-cmdq.c
> > > V4L2 m2m device functions are implemented in mtk-mdp3-m2m.c
> > > Probe, power, suspend/resume, system level functions are defined
> > > in
> > > mtk-mdp3-core.c
> > >
> > > v4l2-compliance 1.22.1, 32 bits, 32-bit time_t
> > >
> > > Compliance test for mtk-mdp3 device /dev/video2:
> > >
> > > Driver Info:
> > > Driver name : mtk-mdp3
> > > Card type : 14001000.mdp3-rdma0
> >
> > Card type is expected to be a human readable name, and that's not
> > the case
> > here.
> >
> > > Bus info : platform:mtk-mdp3
> >
> > <snip>
> >
> > > diff --git a/drivers/media/platform/mediatek/mdp3/mtk-mdp3-m2m.c
> > > b/drivers/media/platform/mediatek/mdp3/mtk-mdp3-m2m.c
> > > new file mode 100644
[snip]
> > > +static const struct vb2_ops mdp_m2m_qops = {
> > > + .queue_setup = mdp_m2m_queue_setup,
> > > + .wait_prepare = vb2_ops_wait_prepare,
> > > + .wait_finish = vb2_ops_wait_finish,
> > > + .buf_prepare = mdp_m2m_buf_prepare,
> > > + .start_streaming = mdp_m2m_start_streaming,
> > > + .stop_streaming = mdp_m2m_stop_streaming,
> > > + .buf_queue = mdp_m2m_buf_queue,
> > > + .buf_out_validate = mdp_m2m_buf_out_validate,
> > > +};
> > > +
> > > +static int mdp_m2m_querycap(struct file *file, void *fh,
> > > + struct v4l2_capability *cap)
> > > +{
> > > + struct mdp_m2m_ctx *ctx = fh_to_ctx(fh);
> > > +
> > > + strscpy(cap->driver, MDP_MODULE_NAME, sizeof(cap->driver));
> > > + strscpy(cap->card, ctx->mdp_dev->pdev->name, sizeof(cap-
> > > >card));
> >
> > As mentioned at the top, this is not a suitable name for cap->card.
> >
> > > + strscpy(cap->bus_info, "platform:mtk-mdp3", sizeof(cap-
> > > >bus_info));
>
> And don't override bus_info, the value isn't right. The V4L2 core
> should
> do the right thing for platform devices now.
>
Hi Laurent,
Thanks for the reminder, I'll fix it in the next version along with
what Hans mentioned earlier.
Regards,
Moudy
> > > + return 0;
> > > +}
> > > +
> > > +static int mdp_m2m_enum_fmt_mplane(struct file *file, void *fh,
> > > + struct v4l2_fmtdesc *f)
> > > +{
> > > + return mdp_enum_fmt_mplane(f);
> > > +}
next prev parent reply other threads:[~2022-07-11 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 7:54 [PATCH v21 0/4] media: mediatek: support mdp3 on mt8183 platform Moudy Ho
2022-07-06 7:54 ` [PATCH v21 1/4] dt-binding: mediatek: add bindings for MediaTek MDP3 components Moudy Ho
2022-07-06 7:54 ` [PATCH v21 2/4] dt-binding: mediatek: add bindings for MediaTek CCORR and WDMA Moudy Ho
2022-07-06 7:54 ` [PATCH v21 3/4] arm64: dts: mt8183: add Mediatek MDP3 nodes Moudy Ho
2022-07-06 7:54 ` [PATCH v21 4/4] media: platform: mtk-mdp3: add Mediatek MDP3 driver Moudy Ho
2022-07-08 8:08 ` [DKIM] " Hans Verkuil
2022-07-08 8:20 ` Laurent Pinchart
2022-07-11 8:25 ` moudy.ho [this message]
2022-07-11 8:11 ` moudy.ho
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=5e3aa17cad22fc8f321fbcc3159ac510f34dc3ea.camel@mediatek.com \
--to=moudy.ho@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=acourbot@chromium.org \
--cc=allen-kh.cheng@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=benjamin.gaignard@collabora.com \
--cc=cellopoint.kai@gmail.com \
--cc=chunkuang.hu@kernel.org \
--cc=daoyuan.huang@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=hsinyi@google.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jason-jh.lin@mediatek.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=pihsun@chromium.org \
--cc=ping-hsun.wu@mediatek.com \
--cc=randy.wu@mediatek.com \
--cc=river.cheng@mediatek.com \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=roy-cw.yeh@mediatek.com \
--cc=tfiga@chromium.org \
--cc=xiandong.wang@mediatek.com \
/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