From: "Kyrie Wu (吴晗)" <Kyrie.Wu@mediatek.com>
To: "nicolas@ndufresne.ca" <nicolas@ndufresne.ca>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"hverkuil-cisco@xs4all.nl" <hverkuil-cisco@xs4all.nl>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: "srv_heupstream@mediatek.com" <srv_heupstream@mediatek.com>
Subject: Re: [PATCH v5 06/12] media: mediatek: jpeg: refactor jpeg buffer payload setting
Date: Fri, 6 Jun 2025 02:50:22 +0000 [thread overview]
Message-ID: <a60a408fb68930dca0e4574386032e6bbf8c1173.camel@mediatek.com> (raw)
In-Reply-To: <ac655c582609b7887381e1b68ed99f6b128fd794.camel@ndufresne.ca>
On Fri, 2025-05-30 at 13:33 -0400, Nicolas Dufresne wrote:
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
>
>
> Hi Kyrie,
>
> Le vendredi 30 mai 2025 à 15:45 +0800, Kyrie Wu a écrit :
> > 1. for multi-core jpegdec:
> > core0: |<-------- decoding buffer0 and resolution changed to
> > smaller
> > core1: |<-------- decoding buffer1
> > core0: |<- handling resolution changing
> > core0: |<- vb2_set_plane_payload
> > 2. the payload size is changed on the step of set format. Because
> > core1
> > is running and streaming has not been stopped, the format cannot be
> > set again, resulting in no change in the payload size.
> > 3. at this time, the payload size is bigger than buffer length,
> > it will print a warnning call trace
> > 4. set payload size must less than buffer length
>
> You'll have to rework the text in this commit message, I must admit I
> don't
> understand from this text what exactly the problem is, make it really
> hard to
> review your solution.
Dear Nicolas,
I'm terribly sorry for the inconvenience caused to you. I will change
the commit message and let it read easier.
Thanks.
>
> >
> > Signed-off-by: Kyrie Wu <kyrie.wu@mediatek.com>
> > ---
> > .../platform/mediatek/jpeg/mtk_jpeg_core.c | 18
> > +++++++++++++++---
> > 1 file changed, 15 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/media/platform/mediatek/jpeg/mtk_jpeg_core.c
> > b/drivers/media/platform/mediatek/jpeg/mtk_jpeg_core.c
> > index 0074d1edb534..52d59bb5c9ad 100644
> > --- a/drivers/media/platform/mediatek/jpeg/mtk_jpeg_core.c
> > +++ b/drivers/media/platform/mediatek/jpeg/mtk_jpeg_core.c
> > @@ -720,10 +720,22 @@ static int mtk_jpeg_buf_prepare(struct
> > vb2_buffer *vb)
> > plane_fmt = q_data->pix_mp.plane_fmt[i];
> > if (ctx->enable_exif &&
> > q_data->fmt->fourcc == V4L2_PIX_FMT_JPEG)
> > - vb2_set_plane_payload(vb, i,
> > plane_fmt.sizeimage +
> > - MTK_JPEG_MAX_EXIF_SIZE)
> > ;
> > + if (vb->planes[i].length >
> > (plane_fmt.sizeimage +
> > + MTK_JPEG_MAX_EXIF_SIZE))
> > + vb2_set_plane_payload(vb, i,
> > + plane_fmt.sizei
> > mage +
> > + MTK_JPEG_MAX_EX
> > IF_SIZE);
> > + else
> > + vb2_set_plane_payload(vb, i,
> > + vb-
> > >planes[i].length);
> > +
> > else
> > - vb2_set_plane_payload(vb,
> > i, plane_fmt.sizeimage);
> > + if (vb->planes[i].length >
> > plane_fmt.sizeimage)
> > + vb2_set_plane_payload(vb, i,
> > + plane_fmt.sizei
> > mage);
> > + else
> > + vb2_set_plane_payload(vb, i,
> > + vb-
> > >planes[i].length);
>
> Is this the same as ?
>
> unsigned long max_size = plane_fmt.sizeimage;
>
> if (ctx->enable_exif && q_data->fmt->fourcc ==
> V4L2_PIX_FMT_JPEG)
> max_size += MTK_JPEG_MAX_EXIF_SIZE;
>
> vb2_set_plane_payload(vb, i, MIN(vb-
> >planes[i].length, max_size));
>
> It is unclear to me how this isn't just a workaround though, looking
> forward
> your reworked commit message.
>
> Nicolas
Yes, Thanks for you suggestion. I will fix it in the next version.
Regards,
Kyrie.
>
> > }
> >
> > return 0;
next prev parent reply other threads:[~2025-06-06 2:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 7:45 [PATCH v5 00/12] Enable jpeg enc & dec multi-hardwares for MT8196 Kyrie Wu
2025-05-30 7:45 ` [PATCH v5 01/12] media: dt-bindings: mediatek,jpeg: Add mediatek, mt8196-jpgdec compatible Kyrie Wu
2025-05-30 7:45 ` [PATCH v5 02/12] media: dt-bindings: mediatek,jpeg: Add mediatek, mt8196-jpgenc compatible Kyrie Wu
2025-05-30 7:45 ` [PATCH v5 03/12] media: mediatek: jpeg: add jpeg compatible Kyrie Wu
2025-05-30 7:45 ` [PATCH v5 04/12] media: mediatek: jpeg: add jpeg smmu sid setting Kyrie Wu
2025-05-30 7:45 ` [PATCH v5 05/12] media: mediatek: jpeg: fix jpeg hw count setting Kyrie Wu
2025-05-30 7:45 ` [PATCH v5 06/12] media: mediatek: jpeg: refactor jpeg buffer payload setting Kyrie Wu
2025-05-30 17:33 ` Nicolas Dufresne
2025-06-06 2:50 ` Kyrie Wu (吴晗) [this message]
2025-05-30 7:45 ` [PATCH v5 07/12] media: mediatek: jpeg: refactor jpeg dst buffer layout Kyrie Wu
2025-05-30 17:38 ` Nicolas Dufresne
2025-06-06 2:54 ` Kyrie Wu (吴晗)
2025-05-30 7:45 ` [PATCH v5 08/12] media: mediatek: jpeg: fix stop streaming flow for multi-core Kyrie Wu
2025-05-30 17:40 ` Nicolas Dufresne
2025-06-06 3:14 ` Kyrie Wu (吴晗)
2025-05-30 7:45 ` [PATCH v5 09/12] media: mediatek: jpeg: refactor multi-core clk suspend and resume setting Kyrie Wu
2025-05-30 17:43 ` Nicolas Dufresne
2025-06-06 3:23 ` Kyrie Wu (吴晗)
2025-06-06 14:34 ` Nicolas Dufresne
2025-05-30 7:45 ` [PATCH v5 10/12] media: mediatek: jpeg: fix decoding buffer number setting timing issue Kyrie Wu
2025-05-30 7:45 ` [PATCH v5 11/12] media: mediatek: jpeg: refactor decoding resolution change operation Kyrie Wu
2025-05-30 7:45 ` [PATCH v5 12/12] media: mediatek: jpeg: fix remove buffer operation for multi-core Kyrie Wu
2025-05-30 17:45 ` [PATCH v5 00/12] Enable jpeg enc & dec multi-hardwares for MT8196 Nicolas Dufresne
2025-06-06 2:45 ` Kyrie Wu (吴晗)
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=a60a408fb68930dca0e4574386032e6bbf8c1173.camel@mediatek.com \
--to=kyrie.wu@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=krzk+dt@kernel.org \
--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=nicolas@ndufresne.ca \
--cc=robh@kernel.org \
--cc=srv_heupstream@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
all inboxes | Powered by JetHome®