From: "Irui Wang (王瑞)" <Irui.Wang@mediatek.com>
To: "sebastian.fricke@collabora.com" <sebastian.fricke@collabora.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Longfei Wang (王龙飞)" <Longfei.Wang@mediatek.com>,
"Tiffany Lin (林慧珊)" <tiffany.lin@mediatek.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"Maoguang Meng (孟毛广)" <Maoguang.Meng@mediatek.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"nicolas.dufresne@collabora.com" <nicolas.dufresne@collabora.com>,
"Yunfei Dong (董云飞)" <Yunfei.Dong@mediatek.com>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"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>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH v2] media: mediatek: vcodec: Handle VP9 superframe bitstream with 8 sub-frames
Date: Mon, 4 Mar 2024 02:00:49 +0000 [thread overview]
Message-ID: <14c9dea999efc16f2f1753a9524f558cf066a244.camel@mediatek.com> (raw)
In-Reply-To: <20240301151344.o7khwhbasnncw2cc@basti-XPS-13-9310>
Dear Sebastian Sir,
Thanks for your reviewing.
I will reword the commit message according to your suggestion, and send
a new patch v3. Thank you very much.
Thanks
Best Regards
On Fri, 2024-03-01 at 16:13 +0100, Sebastian Fricke wrote:
> Hey Irui,
>
> On 29.02.2024 11:02, Irui Wang wrote:
> > The VP9 bitstream has 8 sub-frames into one superframe, the
> > superframe
> > index validate failed when reach 8, modify the index checking so
> > that the
> > last sub-frame can be decoded normally with stateful vp9 decoder.
>
> I find this commit message a bit confusing, you say that you couldn't
> index the last superframe, but then you say that you modify the index
> checking so that you can access the last sub-frame.
>
> I would reword this section, here is my suggestion:
>
> The VP9 bitstream uses superframes, which each contain 8 sub-frames,
> enable accessing the last superframe by increasing the range of the
> index validation as the maximum number of superframes is 8 and not 7.
>
> The rest looks good as already mentioned by Nicolas.
>
> Greetings,
> Sebastian
>
> >
> > Signed-off-by: Irui Wang <irui.wang@mediatek.com>
> > ---
> > changed with v1:
> > - add a new define 'VP9_MAX_SUPER_FRAMES_NUM' for superframes.
> > ---
> > .../mediatek/vcodec/decoder/vdec/vdec_vp9_if.c | 11 ++++++
> > -----
> > 1 file changed, 6 insertions(+), 5 deletions(-)
> >
> > diff --git
> > a/drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_vp9_if.c
> > b/drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_vp9_if.c
> > index 55355fa70090..039082f600c8 100644
> > ---
> > a/drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_vp9_if.c
> > +++
> > b/drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_vp9_if.c
> > @@ -16,6 +16,7 @@
> > #include "../vdec_drv_base.h"
> > #include "../vdec_vpu_if.h"
> >
> > +#define VP9_MAX_SUPER_FRAMES_NUM 8
> > #define VP9_SUPER_FRAME_BS_SZ 64
> > #define MAX_VP9_DPB_SIZE 9
> >
> > @@ -133,11 +134,11 @@ struct vp9_sf_ref_fb {
> > */
> > struct vdec_vp9_vsi {
> > unsigned char sf_bs_buf[VP9_SUPER_FRAME_BS_SZ];
> > - struct vp9_sf_ref_fb sf_ref_fb[VP9_MAX_FRM_BUF_NUM-1];
> > + struct vp9_sf_ref_fb sf_ref_fb[VP9_MAX_SUPER_FRAMES_NUM];
> > int sf_next_ref_fb_idx;
> > unsigned int sf_frm_cnt;
> > - unsigned int sf_frm_offset[VP9_MAX_FRM_BUF_NUM-1];
> > - unsigned int sf_frm_sz[VP9_MAX_FRM_BUF_NUM-1];
> > + unsigned int sf_frm_offset[VP9_MAX_SUPER_FRAMES_NUM];
> > + unsigned int sf_frm_sz[VP9_MAX_SUPER_FRAMES_NUM];
> > unsigned int sf_frm_idx;
> > unsigned int sf_init;
> > struct vdec_fb fb;
> > @@ -526,7 +527,7 @@ static void vp9_swap_frm_bufs(struct
> > vdec_vp9_inst *inst)
> > /* if this super frame and it is not last sub-frame, get next
> > fb for
> > * sub-frame decode
> > */
> > - if (vsi->sf_frm_cnt > 0 && vsi->sf_frm_idx != vsi->sf_frm_cnt -
> > 1)
> > + if (vsi->sf_frm_cnt > 0 && vsi->sf_frm_idx != vsi->sf_frm_cnt)
> > vsi->sf_next_ref_fb_idx = vp9_get_sf_ref_fb(inst);
> > }
> >
> > @@ -735,7 +736,7 @@ static void get_free_fb(struct vdec_vp9_inst
> > *inst, struct vdec_fb **out_fb)
> >
> > static int validate_vsi_array_indexes(struct vdec_vp9_inst *inst,
> > struct vdec_vp9_vsi *vsi) {
> > - if (vsi->sf_frm_idx >= VP9_MAX_FRM_BUF_NUM - 1) {
> > + if (vsi->sf_frm_idx > VP9_MAX_SUPER_FRAMES_NUM) {
> > mtk_vdec_err(inst->ctx, "Invalid vsi->sf_frm_idx=%u.",
> > vsi->sf_frm_idx);
> > return -EIO;
> > }
> > --
> > 2.18.0
> >
> >
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-03-04 2:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 3:02 [PATCH v2] media: mediatek: vcodec: Handle VP9 superframe bitstream with 8 sub-frames Irui Wang
2024-03-01 15:13 ` Sebastian Fricke
2024-03-04 2:00 ` Irui Wang (王瑞) [this message]
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=14c9dea999efc16f2f1753a9524f558cf066a244.camel@mediatek.com \
--to=irui.wang@mediatek.com \
--cc=Longfei.Wang@mediatek.com \
--cc=Maoguang.Meng@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Yunfei.Dong@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--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.dufresne@collabora.com \
--cc=sebastian.fricke@collabora.com \
--cc=tiffany.lin@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