From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: Irui Wang <irui.wang@mediatek.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
angelogioacchino.delregno@collabora.com,
Yunfei Dong <yunfei.dong@mediatek.com>
Cc: Project_Global_Chrome_Upstream_Group@mediatek.com,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Longfei Wang <longfei.wang@mediatek.com>
Subject: Re: [PATCH 0/2] Add support for MT8196 video encoder
Date: Fri, 21 Feb 2025 10:53:17 -0500 [thread overview]
Message-ID: <cd8f43a310f771f7db7ae1ab7fb2f8b5d554c2da.camel@collabora.com> (raw)
In-Reply-To: <20250221031004.9050-1-irui.wang@mediatek.com>
Hi,
Le vendredi 21 février 2025 à 11:10 +0800, Irui Wang a écrit :
> This patch series adds support for MT8196 video encoder. The changes
> include introducing a new encoder driver interface and add support
> for the
> new encoder driver encoding process.
thanks for your contribution. In general, when adding new HW support,
we would like to see in your cover letter your v4l2-compliance report.
Since this is a firmware based encoder, we also want to know how the
process with uploading your firmware in linux-firmware is going. We can
do reviews ahead of this of course, but merging depends on having
firmware upstream. We did some favours in the past and it worked for
many SoC, but things seems to have changed lately with the MT8188
firmware situation. Hope you understand this concern.
regards,
Nicolas
>
> Irui Wang (2):
> media: mediatek: encoder: Add a new encoder driver interface
> media: mediatek: encoder: Add support for common driver encode
> process
>
> .../platform/mediatek/vcodec/encoder/Makefile | 1 +
> .../mediatek/vcodec/encoder/mtk_vcodec_enc.c | 2 +
> .../vcodec/encoder/mtk_vcodec_enc_drv.h | 3 +
> .../vcodec/encoder/venc/venc_common_if.c | 704
> ++++++++++++++++++
> .../mediatek/vcodec/encoder/venc_drv_if.c | 3 +-
> .../mediatek/vcodec/encoder/venc_drv_if.h | 3 +
> .../mediatek/vcodec/encoder/venc_ipi_msg.h | 26 +
> .../mediatek/vcodec/encoder/venc_vpu_if.c | 37 +-
> 8 files changed, 764 insertions(+), 15 deletions(-)
> create mode 100644
> drivers/media/platform/mediatek/vcodec/encoder/venc/venc_common_if.c
>
next prev parent reply other threads:[~2025-02-21 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 3:10 [PATCH 0/2] Add support for MT8196 video encoder Irui Wang
2025-02-21 3:10 ` [PATCH 1/2] media: mediatek: encoder: Add a new encoder driver interface Irui Wang
2025-04-28 21:14 ` Nicolas Dufresne
2025-04-29 3:10 ` Irui Wang (王瑞)
2025-02-21 3:10 ` [PATCH 2/2] media: mediatek: encoder: Add support for common driver encode process Irui Wang
2025-02-21 15:53 ` Nicolas Dufresne [this message]
2025-02-24 2:10 ` [PATCH 0/2] Add support for MT8196 video encoder 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=cd8f43a310f771f7db7ae1ab7fb2f8b5d554c2da.camel@collabora.com \
--to=nicolas.dufresne@collabora.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=irui.wang@mediatek.com \
--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=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--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