From: "Yunfei Dong (董云飞)" <Yunfei.Dong@mediatek.com>
To: "wenst@chromium.org" <wenst@chromium.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"frkoenig@chromium.org" <frkoenig@chromium.org>,
"stevecho@chromium.org" <stevecho@chromium.org>,
"nhebert@chromium.org" <nhebert@chromium.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"nicolas.dufresne@collabora.com" <nicolas.dufresne@collabora.com>,
"daniel.almeida@collabora.com" <daniel.almeida@collabora.com>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"benjamin.gaignard@collabora.com"
<benjamin.gaignard@collabora.com>,
"sebastian.fricke@collabora.com" <sebastian.fricke@collabora.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"hverkuil-cisco@xs4all.nl" <hverkuil-cisco@xs4all.nl>,
"hsinyi@chromium.org" <hsinyi@chromium.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"Nicolas Prado" <nfraprado@collabora.com>
Subject: Re: [PATCH 2/6] media: mediatek: vcodec: remove parse nal info in kernel
Date: Wed, 16 Oct 2024 03:46:54 +0000 [thread overview]
Message-ID: <c1d16832821ce4812ced2adb3b618a732b66bd82.camel@mediatek.com> (raw)
In-Reply-To: <CAGXv+5H4FsadBheokwO7hTxDxAtYakL15Ki+EcnhQ3Unbz3o9w@mail.gmail.com>
Hi Chen-Yu,
Thanks for your help to review the patch.
On Tue, 2024-10-15 at 15:58 +0800, Chen-Yu Tsai wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> On Mon, Oct 14, 2024 at 3:33 PM Yunfei Dong <
> yunfei.dong@mediatek.com> wrote:
> >
> > Hardware can parse the slice synatx to get nal information in
> > scp, needn't to parse it in kernel again.
>
> Does this apply to all existing shipped SCP firmware? If not, please
> put this behind a vdec firmware flag.
>
Need to remove the parse driver for extend driver, keep the logic for
non extend architecture.
> ChenYu
>
Best Regards,
Yunfei Dong
>
> > Signed-off-by: Yunfei Dong <yunfei.dong@mediatek.com>
> > ---
> > .../vcodec/decoder/vdec/vdec_h264_req_multi_if.c | 13 ++-------
> ----
> > 1 file changed, 2 insertions(+), 11 deletions(-)
> >
> > diff --git
> a/drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_h264_req_m
> ulti_if.c
> b/drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_h264_req_m
> ulti_if.c
> > index d3f8d62238c0..76b96924a2a7 100644
> > ---
> a/drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_h264_req_m
> ulti_if.c
> > +++
> b/drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_h264_req_m
> ulti_if.c
> > @@ -634,11 +634,10 @@ static int vdec_h264_slice_lat_decode(void
> *h_vdec, struct mtk_vcodec_mem *bs,
> > struct vdec_h264_slice_inst *inst = h_vdec;
> > struct vdec_vpu_inst *vpu = &inst->vpu;
> > struct mtk_video_dec_buf *src_buf_info;
> > - int nal_start_idx, err, timeout = 0;
> > + int err, timeout = 0;
> > unsigned int data[2];
> > struct vdec_lat_buf *lat_buf;
> > struct vdec_h264_slice_share_info *share_info;
> > - unsigned char *buf;
> >
> > if (vdec_msg_queue_init(&inst->ctx->msg_queue, inst->ctx,
> > vdec_h264_slice_core_decode,
> > @@ -662,14 +661,6 @@ static int vdec_h264_slice_lat_decode(void
> *h_vdec, struct mtk_vcodec_mem *bs,
> > share_info = lat_buf->private_data;
> > src_buf_info = container_of(bs, struct mtk_video_dec_buf,
> bs_buffer);
> >
> > - buf = (unsigned char *)bs->va;
> > - nal_start_idx = mtk_vdec_h264_find_start_code(buf, bs-
> >size);
> > - if (nal_start_idx < 0) {
> > - err = -EINVAL;
> > - goto err_free_fb_out;
> > - }
> > -
> > - inst->vsi->dec.nal_info = buf[nal_start_idx];
> > lat_buf->vb2_v4l2_src = &src_buf_info->m2m_buf.vb;
> > v4l2_m2m_buf_copy_metadata(&src_buf_info->m2m_buf.vb,
> &lat_buf->ts_info, true);
> >
> > @@ -677,7 +668,7 @@ static int vdec_h264_slice_lat_decode(void
> *h_vdec, struct mtk_vcodec_mem *bs,
> > if (err)
> > goto err_free_fb_out;
> >
> > - vdec_h264_insert_startcode(inst->ctx->dev, buf, &bs->size,
> > + vdec_h264_insert_startcode(inst->ctx->dev, bs->va, &bs-
> >size,
> > &share_info-
> >h264_slice_params.pps);
> >
> > *res_chg = inst->resolution_changed;
> > --
> > 2.46.0
> >
> >
next prev parent reply other threads:[~2024-10-16 3:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 7:33 [PATCH 0/6] media: mediatek: vcodec: support h264 extend vsi Yunfei Dong
2024-10-14 7:33 ` [PATCH 1/6] media: mediatek: vcodec: extend h264 video share information Yunfei Dong
2024-10-14 7:33 ` [PATCH 2/6] media: mediatek: vcodec: remove parse nal info in kernel Yunfei Dong
2024-10-15 7:58 ` Chen-Yu Tsai
2024-10-16 3:46 ` Yunfei Dong (董云飞) [this message]
2024-10-14 7:33 ` [PATCH 3/6] media: mediatek: vcodec: remove vsi operation in common interface Yunfei Dong
2024-10-14 7:33 ` [PATCH 4/6] media: mediatek: vcodec: rename vsi to extend vsi Yunfei Dong
2024-10-14 7:33 ` [PATCH 5/6] media: mediatek: vcodec: adding non extend struct Yunfei Dong
2024-10-14 7:33 ` [PATCH 6/6] media: mediatek: vcodec: support extend h264 driver Yunfei Dong
2024-10-15 7:54 ` [PATCH 0/6] media: mediatek: vcodec: support h264 extend vsi Chen-Yu Tsai
2024-10-16 3:44 ` Yunfei Dong (董云飞)
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=c1d16832821ce4812ced2adb3b618a732b66bd82.camel@mediatek.com \
--to=yunfei.dong@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=benjamin.gaignard@collabora.com \
--cc=daniel.almeida@collabora.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=frkoenig@chromium.org \
--cc=hsinyi@chromium.org \
--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=nfraprado@collabora.com \
--cc=nhebert@chromium.org \
--cc=nicolas.dufresne@collabora.com \
--cc=sebastian.fricke@collabora.com \
--cc=stevecho@chromium.org \
--cc=wenst@chromium.org \
/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).