From: Yunfei Dong <yunfei.dong@mediatek.com>
To: "Nícolas F . R . A . Prado" <nfraprado@collabora.com>,
"Sebastian Fricke" <sebastian.fricke@collabora.com>,
"Nicolas Dufresne" <nicolas.dufresne@collabora.com>,
"Hans Verkuil" <hverkuil-cisco@xs4all.nl>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Benjamin Gaignard" <benjamin.gaignard@collabora.com>,
"Nathan Hebert" <nhebert@chromium.org>,
"Daniel Almeida" <daniel.almeida@collabora.com>
Cc: Hsin-Yi Wang <hsinyi@chromium.org>,
Fritz Koenig <frkoenig@chromium.org>,
Daniel Vetter <daniel@ffwll.ch>,
Steve Cho <stevecho@chromium.org>,
"Yunfei Dong" <yunfei.dong@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>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: [PATCH 0/6] media: mediatek: vcodec: support h264 extend vsi
Date: Mon, 14 Oct 2024 15:33:04 +0800 [thread overview]
Message-ID: <20241014073314.18409-1-yunfei.dong@mediatek.com> (raw)
The working buffer address start and end are calculated in kernel
side currently, can't calculate the address end if the driver only
getting the address file handle, not the real physical address. Need
to extend the vsi to calculate the address end in scp.
Re-construct some interface and add config to support extend and non
extend at the same time.
---
This patch series depends on:
[1] https://patchwork.kernel.org/project/linux-mediatek/cover/20241012064333.27269-1-yunfei.dong@mediatek.com
---
Yunfei Dong (6):
media: mediatek: vcodec: extend h264 video share information
media: mediatek: vcodec: remove parse nal info in kernel
media: mediatek: vcodec: remove vsi operation in common interface
media: mediatek: vcodec: rename vsi to extend vsi
media: mediatek: vcodec: adding non extend struct
media: mediatek: vcodec: support extend h264 driver
.../vcodec/decoder/mtk_vcodec_dec_drv.h | 2 +
.../decoder/vdec/vdec_h264_req_multi_if.c | 516 +++++++++++++++++-
2 files changed, 493 insertions(+), 25 deletions(-)
--
2.46.0
next reply other threads:[~2024-10-14 7:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 7:33 Yunfei Dong [this message]
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 (董云飞)
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=20241014073314.18409-1-yunfei.dong@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 \
/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).