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: [V5,3/8] media: mtk-jpegdec: manage jpegdec multi-hardware
Date: Mon, 25 Jul 2022 10:14:06 +0800 [thread overview]
Message-ID: <788c192e17d1fa88105a9bb5238a023e593b251b.camel@mediatek.com> (raw)
In-Reply-To: <00dc6bff-d87a-0d80-fe20-ae70e5ad0c4f@collabora.com>
On Mon, 2022-07-18 at 12:22 +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/HW1/HW2.
> >
> > Signed-off-by: kyrie wu <kyrie.wu@mediatek.com>
> > Signed-off-by: irui wang <irui.wang@mediatek.com>
> >
> > ---
> > drivers/media/platform/mediatek/jpeg/Makefile | 5 +-
> > .../platform/mediatek/jpeg/mtk_jpeg_core.c | 23 +++
> > .../platform/mediatek/jpeg/mtk_jpeg_core.h | 37 ++++
> > .../platform/mediatek/jpeg/mtk_jpeg_dec_hw.c | 172
> > ++++++++++++++++++
> > 4 files changed, 235 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/media/platform/mediatek/jpeg/Makefile
> > b/drivers/media/platform/mediatek/jpeg/Makefile
> > index 69703db4b0a5..26e84852523e 100644
> > --- a/drivers/media/platform/mediatek/jpeg/Makefile
> > +++ b/drivers/media/platform/mediatek/jpeg/Makefile
> > @@ -1,9 +1,10 @@
> > # SPDX-License-Identifier: GPL-2.0-only
> > obj-$(CONFIG_VIDEO_MEDIATEK_JPEG) += mtk_jpeg.o \
> > - mtk-jpeg-enc-hw.o
> > + mtk-jpeg-enc-hw.o \
> > + mtk-jpeg-dec-hw.o
> >
> > mtk_jpeg-y := mtk_jpeg_core.o \
> > - mtk_jpeg_dec_hw.o \
> > mtk_jpeg_dec_parse.o
> >
> > mtk-jpeg-enc-hw-y := mtk_jpeg_enc_hw.o
> > +mtk-jpeg-dec-hw-y := mtk_jpeg_dec_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 386d48cc4f59..a9e8be976bb0 100644
> > --- a/drivers/media/platform/mediatek/jpeg/mtk_jpeg_core.c
> > +++ b/drivers/media/platform/mediatek/jpeg/mtk_jpeg_core.c
> > @@ -1100,6 +1100,10 @@ static void
> > mtk_jpeg_multicore_enc_device_run(void *priv)
> > queue_work(jpeg->workqueue, &ctx->jpeg_work);
> > }
> >
> > +static void mtk_jpeg_multicore_dec_device_run(void *priv)
> > +{
>
> .... why is this function empty?!
>
> > +}
> > +
> > static void mtk_jpeg_dec_device_run(void *priv)
> > {
> > struct mtk_jpeg_ctx *ctx = priv;
> > @@ -1166,6 +1170,10 @@ static const struct v4l2_m2m_ops
> > mtk_jpeg_multicore_enc_m2m_ops = {
> > .device_run = mtk_jpeg_multicore_enc_device_run,
> > };
> >
> > +static const struct v4l2_m2m_ops mtk_jpeg_multicore_dec_m2m_ops =
> > {
> > + .device_run = mtk_jpeg_multicore_dec_device_run,
> > +};
> > +
> > static const struct v4l2_m2m_ops mtk_jpeg_dec_m2m_ops = {
> > .device_run = mtk_jpeg_dec_device_run,
> > .job_ready = mtk_jpeg_dec_job_ready,
> > @@ -1680,6 +1688,17 @@ static struct mtk_jpeg_variant
> > mtk8195_jpegenc_drvdata = {
> > .cap_q_default_fourcc = V4L2_PIX_FMT_JPEG,
> > };
> >
> > +static const struct mtk_jpeg_variant mtk8195_jpegdec_drvdata = {
> > + .formats = mtk_jpeg_dec_formats,
> > + .num_formats = MTK_JPEG_DEC_NUM_FORMATS,
> > + .qops = &mtk_jpeg_dec_qops,
> > + .m2m_ops = &mtk_jpeg_multicore_dec_m2m_ops,
> > + .dev_name = "mtk-jpeg-dec",
> > + .ioctl_ops = &mtk_jpeg_dec_ioctl_ops,
> > + .out_q_default_fourcc = V4L2_PIX_FMT_JPEG,
> > + .cap_q_default_fourcc = V4L2_PIX_FMT_YUV420M,
> > +};
> > +
> > #if defined(CONFIG_OF)
> > static const struct of_device_id mtk_jpeg_match[] = {
> > {
> > @@ -1698,6 +1717,10 @@ static const struct of_device_id
> > mtk_jpeg_match[] = {
> > .compatible = "mediatek,mt8195-jpgenc",
> > .data = &mtk8195_jpegenc_drvdata,
> > },
> > + {
> > + .compatible = "mediatek,mt8195-jpgdec",
> > + .data = &mtk8195_jpegdec_drvdata,
> > + },
> > {},
> > };
> >
>
> ..snip..
>
> > diff --git a/drivers/media/platform/mediatek/jpeg/mtk_jpeg_dec_hw.c
> > b/drivers/media/platform/mediatek/jpeg/mtk_jpeg_dec_hw.c
> > index d2f25f43e852..232e81165dd3 100644
> > --- a/drivers/media/platform/mediatek/jpeg/mtk_jpeg_dec_hw.c
> > +++ b/drivers/media/platform/mediatek/jpeg/mtk_jpeg_dec_hw.c
>
> ..snip..
>
> > +
> > +static int mtk_jpegdec_hw_probe(struct platform_device *pdev)
> > +{
> > + struct mtk_jpegdec_clk *jpegdec_clk;
> > + struct mtk_jpeg_dev *master_dev;
> > + struct mtk_jpegdec_comp_dev *dev;
> > + int ret, i;
> > +
> > + struct device *decs = &pdev->dev;
> > +
> > + if (!decs->parent)
> > + return -EPROBE_DEFER;
> > +
> > + master_dev = dev_get_drvdata(decs->parent);
> > + if (!master_dev)
> > + return -EPROBE_DEFER;
> > +
> > + dev = devm_kzalloc(&pdev->dev, sizeof(*dev), GFP_KERNEL);
> > + if (!dev)
> > + return -ENOMEM;
> > +
> > + dev->plat_dev = pdev;
> > + dev->dev = &pdev->dev;
> > +
> > + if (!master_dev->is_jpgdec_multihw) {
> > + master_dev->is_jpgdec_multihw = true;
> > + for (i = 0; i < MTK_JPEGDEC_HW_MAX; i++)
> > + master_dev->dec_hw_dev[i] = NULL;
> > + }
> > +
> > + jpegdec_clk = &dev->jdec_clk;
> > +
> > + jpegdec_clk->clk_num = devm_clk_bulk_get_all(&pdev->dev,
> > + &jpegdec_clk-
> > >clks);
> > + if (jpegdec_clk->clk_num < 0)
> > + return dev_err_probe(&pdev->dev,
> > + jpegdec_clk->clk_num,
> > + "Failed to get jpegdec clock
> > count.\n");
> > +
> > + dev->reg_base = devm_platform_ioremap_resource(pdev, 0);
> > + if (IS_ERR(dev->reg_base))
> > + return PTR_ERR(dev->reg_base);
> > +
> > + ret = mtk_jpegdec_hw_init_irq(dev);
> > + if (ret)
> > + return dev_err_probe(&pdev->dev,
> > + ret,
> > + "Failed to register JPEGDEC irq
> > handler.\n");
>
> Fix:
> return dev_err_probe(&pdev->dev, ret,
>
> "Failed to register JPEGDEC irq
> handler.\n");
>
>
> Regards,
> Angelo
Hi Angelo,
Thanks for your checking.
Regards,
Kyrie.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-25 2:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 9:34 [V5,0/8] Support multi-hardware jpeg decoder for MT8195 Irui Wang
2022-07-16 9:34 ` [V5,1/8] dt-bindings: mediatek: Add mediatek,mt8195-jpgdec compatible Irui Wang
2022-07-18 1:43 ` Rob Herring
2022-07-18 8:27 ` kyrie.wu
2022-07-16 9:34 ` [V5,2/8] media: mtk-jpegdec: export jpeg decoder functions Irui Wang
2022-07-16 9:34 ` [V5,3/8] media: mtk-jpegdec: manage jpegdec multi-hardware Irui Wang
2022-07-18 10:22 ` AngeloGioacchino Del Regno
2022-07-25 2:14 ` kyrie.wu [this message]
2022-07-16 9:34 ` [V5,4/8] media: mtk-jpegdec: add jpegdec timeout func interface Irui Wang
2022-07-16 9:34 ` [V5,5/8] media: mtk-jpegdec: add jpeg decode worker interface Irui Wang
2022-07-18 10:33 ` AngeloGioacchino Del Regno
2022-07-25 2:17 ` kyrie.wu
2022-07-16 9:34 ` [V5,6/8] media: mtk-jpegdec: add output pic reorder interface Irui Wang
2022-07-18 10:36 ` AngeloGioacchino Del Regno
2022-07-25 2:19 ` kyrie.wu
2022-07-16 9:34 ` [V5,7/8] media: mtk-jpegdec: refactor jpegdec func interface Irui Wang
2022-07-16 9:34 ` [V5,8/8] mtk-jpegdec: add stop cmd interface for jpgdec 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=788c192e17d1fa88105a9bb5238a023e593b251b.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;
as well as URLs for NNTP newsgroup(s).