From: kyrie.wu <kyrie.wu@mediatek.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Irui Wang <irui.wang@mediatek.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Tzung-Bi Shih <tzungbi@chromium.org>,
<nicolas.dufresne@collabora.com>, <wenst@chromium.org>
Cc: <Project_Global_Chrome_Upstream_Group@mediatek.com>,
<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>,
Tomasz Figa <tfiga@chromium.org>, <xia.jiang@mediatek.com>,
<maoguang.meng@mediatek.com>, <srv_heupstream@mediatek.com>
Subject: Re: [V11,3/7] mtk-jpegenc: manage jpegenc multi-hardware
Date: Mon, 25 Jul 2022 09:53:17 +0800 [thread overview]
Message-ID: <dd9c3ff6ad081627ff9419d6f08995ea06cad820.camel@mediatek.com> (raw)
In-Reply-To: <f8618c29-167b-a627-e4b1-d117ec860b7e@collabora.com>
On Mon, 2022-07-18 at 12:40 +0200, AngeloGioacchino Del Regno wrote:
> Il 16/07/22 11:34, Irui Wang ha scritto:
> > From: kyrie wu <kyrie.wu@mediatek.com>
> >
> > manage each hardware information, including irq/clk/power.
> > the hardware includes HW0 and HW1.
> >
> > Signed-off-by: kyrie wu <kyrie.wu@mediatek.com>
> > Signed-off-by: irui wang <irui.wang@mediatek.com>
> >
> > ---
> > drivers/media/platform/mediatek/jpeg/Makefile | 11 +-
> > .../platform/mediatek/jpeg/mtk_jpeg_core.c | 94 ++++++----
> > .../platform/mediatek/jpeg/mtk_jpeg_core.h | 37 ++++
> > .../platform/mediatek/jpeg/mtk_jpeg_enc_hw.c | 163
> > ++++++++++++++++++
> > 4 files changed, 272 insertions(+), 33 deletions(-)
> >
> > diff --git a/drivers/media/platform/mediatek/jpeg/Makefile
> > b/drivers/media/platform/mediatek/jpeg/Makefile
> > index 76c33aad0f3f..69703db4b0a5 100644
> > --- a/drivers/media/platform/mediatek/jpeg/Makefile
> > +++ b/drivers/media/platform/mediatek/jpeg/Makefile
> > @@ -1,6 +1,9 @@
> > # SPDX-License-Identifier: GPL-2.0-only
> > -mtk_jpeg-objs := mtk_jpeg_core.o \
> > +obj-$(CONFIG_VIDEO_MEDIATEK_JPEG) += mtk_jpeg.o \
> > + mtk-jpeg-enc-hw.o
> > +
> > +mtk_jpeg-y := mtk_jpeg_core.o \
> > mtk_jpeg_dec_hw.o \
> > - mtk_jpeg_dec_parse.o \
> > - mtk_jpeg_enc_hw.o
> > -obj-$(CONFIG_VIDEO_MEDIATEK_JPEG) += mtk_jpeg.o
> > + mtk_jpeg_dec_parse.o
> > +
> > +mtk-jpeg-enc-hw-y := mtk_jpeg_enc_hw.o
> > diff --git a/drivers/media/platform/mediatek/jpeg/mtk_jpeg_core.c
> > b/drivers/media/platform/mediatek/jpeg/mtk_jpeg_core.c
> > index 724fb7aeb0ee..3286e9606505 100644
> > --- a/drivers/media/platform/mediatek/jpeg/mtk_jpeg_core.c
> > +++ b/drivers/media/platform/mediatek/jpeg/mtk_jpeg_core.c
>
> ..snip..
>
> > @@ -1497,6 +1516,18 @@ static const struct mtk_jpeg_variant
> > mtk_jpeg_drvdata = {
> > .cap_q_default_fourcc = V4L2_PIX_FMT_JPEG,
> > };
> >
> > +static struct mtk_jpeg_variant mtk8195_jpegenc_drvdata = {
>
> mt8195_jpegenc_drvdata, or mtk_jpegenc_multicore_drvdata
>
> (same applies for jpegdec)
>
> > + .formats = mtk_jpeg_enc_formats,
> > + .num_formats = MTK_JPEG_ENC_NUM_FORMATS,
> > + .qops = &mtk_jpeg_enc_qops,
> > + .m2m_ops = &mtk_jpeg_multicore_enc_m2m_ops,
>
> Same comment for jpgenc as well: add support for this device after
> adding support
> for multicore encoder.
Hi Angelo,
Thanks for your suggestion, I will fix it in the next version.
Regards,
Kyrie.
>
> > + .dev_name = "mtk-jpeg-enc",
> > + .ioctl_ops = &mtk_jpeg_enc_ioctl_ops,
> > + .out_q_default_fourcc = V4L2_PIX_FMT_YUYV,
> > + .cap_q_default_fourcc = V4L2_PIX_FMT_JPEG,
> > +};
> > +
> > +#if defined(CONFIG_OF)
> > static const struct of_device_id mtk_jpeg_match[] = {
> > {
> > .compatible = "mediatek,mt8173-jpgdec",
> > @@ -1510,10 +1541,15 @@ static const struct of_device_id
> > mtk_jpeg_match[] = {
> > .compatible = "mediatek,mtk-jpgenc",
> > .data = &mtk_jpeg_drvdata,
> > },
> > + {
> > + .compatible = "mediatek,mt8195-jpgenc",
> > + .data = &mtk8195_jpegenc_drvdata,
> > + },
> > {},
> > };
> >
> > MODULE_DEVICE_TABLE(of, mtk_jpeg_match);
> > +#endif
> >
> > static struct platform_driver mtk_jpeg_driver = {
> > .probe = mtk_jpeg_probe,
>
>
>
>
next prev parent reply other threads:[~2022-07-25 1:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 9:34 [V11,0/7] Enable two hardware jpeg encoder for MT8195 Irui Wang
2022-07-16 9:34 ` [V11,1/7] dt-bindings: mediatek: Add mediatek, mt8195-jpgenc compatible Irui Wang
2022-07-18 1:43 ` Rob Herring
2022-07-18 8:29 ` kyrie.wu
2022-07-16 9:34 ` [V11,2/7] mtk-jpegenc: export jpeg encoder functions Irui Wang
2022-07-16 9:34 ` [V11,3/7] mtk-jpegenc: manage jpegenc multi-hardware Irui Wang
2022-07-18 10:40 ` AngeloGioacchino Del Regno
2022-07-25 1:53 ` kyrie.wu [this message]
2022-07-16 9:34 ` [V11,4/7] mtk-jpegenc: add jpegenc timeout func interface Irui Wang
2022-07-16 9:34 ` [V11,5/7] mtk-jpegenc: add jpeg encode worker interface Irui Wang
2022-07-16 9:34 ` [V11,6/7] mtk-jpegenc: add output pic reorder interface Irui Wang
2022-07-16 9:34 ` [V11,7/7] mtk-jpegenc: add stop cmd interface for jpgenc Irui Wang
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=dd9c3ff6ad081627ff9419d6f08995ea06cad820.camel@mediatek.com \
--to=kyrie.wu@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=irui.wang@mediatek.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=maoguang.meng@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=robh+dt@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@chromium.org \
--cc=tzungbi@chromium.org \
--cc=wenst@chromium.org \
--cc=xia.jiang@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