From: Yunfei Dong <yunfei.dong@mediatek.com>
To: "Sebastian Fricke" <sebastian.fricke@collabora.com>,
"Nícolas F . R . A . Prado" <nfraprado@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>
Cc: Chen-Yu Tsai <wenst@chromium.org>,
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 v2,0/7] media: mediatek: vcodec: Set the correct profile and level for each platform
Date: Mon, 23 Oct 2023 11:06:33 +0800 [thread overview]
Message-ID: <20231023030640.16393-1-yunfei.dong@mediatek.com> (raw)
The supported maximum resolution, bit and frame rate of different platform
for each spec are not always the same, need to set the correct level and
and profile values according to the chip name.
patch 1 get the chip name for each platform
patch 2~3 set h264 and h265 level
patch 4~5 set h264 and h265 profile
patch 6~7 set vp9 level and profile
changed with v1:
- Change the commit message for each patch.
- Change the supported level for mt8195 and mt8192
---
Yunfei Dong (7):
media: mediatek: vcodec: Get the chip name for each platform
media: mediatek: vcodec: Set the supported h264 level for each
platform
media: mediatek: vcodec: Set the supported h265 level for each
platform
media: mediatek: vcodec: Set the supported h264 profile for each
platform
media: mediatek: vcodec: Set the supported h265 profile for each
platform
media: mediatek: vcodec: Set the supported vp9 level for each platform
media: mediatek: vcodec: Set the supported vp9 profile for each
platform
.../mediatek/vcodec/decoder/mtk_vcodec_dec.c | 24 +--
.../vcodec/decoder/mtk_vcodec_dec_drv.c | 26 +++
.../vcodec/decoder/mtk_vcodec_dec_drv.h | 14 ++
.../vcodec/decoder/mtk_vcodec_dec_stateless.c | 168 +++++++++++++++++-
4 files changed, 208 insertions(+), 24 deletions(-)
--
2.18.0
next reply other threads:[~2023-10-23 3:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 3:06 Yunfei Dong [this message]
2023-10-23 3:06 ` [PATCH v2,1/7] media: mediatek: vcodec: Get the chip name " Yunfei Dong
2023-10-23 3:06 ` [PATCH v2,2/7] media: mediatek: vcodec: Set the supported h264 level " Yunfei Dong
2023-10-23 8:56 ` AngeloGioacchino Del Regno
2023-10-23 3:06 ` [PATCH v2,3/7] media: mediatek: vcodec: Set the supported h265 " Yunfei Dong
2023-10-23 8:56 ` AngeloGioacchino Del Regno
2023-10-23 3:06 ` [PATCH v2,4/7] media: mediatek: vcodec: Set the supported h264 profile " Yunfei Dong
2023-10-23 8:56 ` AngeloGioacchino Del Regno
2023-10-23 3:06 ` [PATCH v2,5/7] media: mediatek: vcodec: Set the supported h265 " Yunfei Dong
2023-10-23 8:56 ` AngeloGioacchino Del Regno
2023-10-23 3:06 ` [PATCH v2,6/7] media: mediatek: vcodec: Set the supported vp9 level " Yunfei Dong
2023-10-23 8:56 ` AngeloGioacchino Del Regno
2023-10-23 3:06 ` [PATCH v2,7/7] media: mediatek: vcodec: Set the supported vp9 profile " Yunfei Dong
2023-10-23 8:56 ` AngeloGioacchino Del Regno
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=20231023030640.16393-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@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
all inboxes | Powered by JetHome®