From: Irui Wang <irui.wang@mediatek.com>
To: Alexandre Courbot <acourbot@chromium.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Tiffany Lin <tiffany.lin@mediatek.com>,
Andrew-CT Chen <andrew-ct.chen@mediatek.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Tomasz Figa <tfiga@google.com>,
Hsin-Yi Wang <hsinyi@chromium.org>,
Maoguang Meng <maoguang.meng@mediatek.com>,
Longfei Wang <longfei.wang@mediatek.com>,
Yunfei Dong <yunfei.dong@mediatek.com>, <yong.wu@mediatek.com>
Cc: Irui Wang <irui.wang@mediatek.com>, <linux-media@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<srv_heupstream@mediatek.com>,
<linux-mediatek@lists.infradead.org>
Subject: [PATCH v2,0/5] Support H264 4K on MT8192
Date: Fri, 12 Mar 2021 15:55:37 +0800 [thread overview]
Message-ID: <20210312075542.5503-1-irui.wang@mediatek.com> (raw)
Add MT8192 H264 venc driver and support H264 4K encoding on MT8192.
Signed-off-by: Irui Wang <irui.wang@mediatek.com>
---
This patch dependents on
"dt-bindings: media: mtk-vcodec: Separating mtk vcodec encoder node" [1]
We need "core_id" variable in device private data to indicate
current encoder driver.
Please also accept this patch together with [1].
http://lists.infradead.org/pipermail/linux-mediatek/2021-March/022432.html
---
Change since v1:
- remove encoder device tree example in dt-bindings
---
Irui Wang (5):
dt-bindings: media: mtk-vcodec: Add dma-ranges property
media: mtk-vcodec: Support 4GB~8GB range iova space for venc
dt-bindings: media: mtk-vcodec: Add binding for MT8192 VENC
media: mtk-vcodec: Add MT8192 H264 venc driver
media: mtk-vcodec: Support H264 4K encoding on MT8192
.../bindings/media/mediatek-vcodec.txt | 3 +
.../platform/mtk-vcodec/mtk_vcodec_drv.h | 1 +
.../platform/mtk-vcodec/mtk_vcodec_enc.c | 58 ++++++++++++++-----
.../platform/mtk-vcodec/mtk_vcodec_enc_drv.c | 18 ++++++
.../platform/mtk-vcodec/venc/venc_h264_if.c | 4 ++
5 files changed, 69 insertions(+), 15 deletions(-)
--
2.18.0
next reply other threads:[~2021-03-12 7:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 7:55 Irui Wang [this message]
2021-03-12 7:55 ` [PATCH v2,1/5] dt-bindings: media: mtk-vcodec: Add dma-ranges property Irui Wang
2021-03-12 7:55 ` [PATCH v2,2/5] media: mtk-vcodec: Support 4GB~8GB range iova space for venc Irui Wang
2021-03-12 7:55 ` [PATCH v2,3/5] dt-bindings: media: mtk-vcodec: Add binding for MT8192 VENC Irui Wang
2021-03-24 16:00 ` [PATCH v2, 3/5] " Rob Herring
2021-03-12 7:55 ` [PATCH v2,4/5] media: mtk-vcodec: Add MT8192 H264 venc driver Irui Wang
2021-03-12 7:55 ` [PATCH v2,5/5] media: mtk-vcodec: Support H264 4K encoding on MT8192 Irui Wang
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=20210312075542.5503-1-irui.wang@mediatek.com \
--to=irui.wang@mediatek.com \
--cc=acourbot@chromium.org \
--cc=andrew-ct.chen@mediatek.com \
--cc=devicetree@vger.kernel.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=longfei.wang@mediatek.com \
--cc=maoguang.meng@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@google.com \
--cc=tiffany.lin@mediatek.com \
--cc=yong.wu@mediatek.com \
--cc=yunfei.dong@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;
as well as URLs for NNTP newsgroup(s).