Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Irui Wang (王瑞)" <Irui.Wang@mediatek.com>
To: "matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"mchehab@kernel.org" <mchehab@kernel.org>,
	"AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>,
	"nicolas.dufresne@collabora.com" <nicolas.dufresne@collabora.com>,
	"hverkuil-cisco@xs4all.nl" <hverkuil-cisco@xs4all.nl>,
	"Yunfei Dong (董云飞)" <Yunfei.Dong@mediatek.com>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"Longfei Wang (王龙飞)" <Longfei.Wang@mediatek.com>,
	Project_Global_Chrome_Upstream_Group
	<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH 0/2] Add support for MT8196 video encoder
Date: Mon, 24 Feb 2025 02:10:34 +0000	[thread overview]
Message-ID: <bee94bf8c47e66beb4021b19e6d0cde8ca829b20.camel@mediatek.com> (raw)
In-Reply-To: <cd8f43a310f771f7db7ae1ab7fb2f8b5d554c2da.camel@collabora.com>

Dear Nicolas,

Thanks for your help reviewing.

On Fri, 2025-02-21 at 10:53 -0500, Nicolas Dufresne wrote:
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> 
> 
> 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.

OK, we will add the v4l2-compliance report in next version.

> 
> 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.

Thanks for your ahead of reviewing, we also want to send our patches
for reviewing in advance to save some times. Certainly, the patches
should be merged depends on firmware, we could do both things
simultaneously.

Thank you again for your help.
> 
> 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
> > 

      reply	other threads:[~2025-02-24  2:12 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 ` [PATCH 0/2] Add support for MT8196 video encoder Nicolas Dufresne
2025-02-24  2:10   ` Irui Wang (王瑞) [this message]

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=bee94bf8c47e66beb4021b19e6d0cde8ca829b20.camel@mediatek.com \
    --to=irui.wang@mediatek.com \
    --cc=Longfei.Wang@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=Yunfei.Dong@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --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=matthias.bgg@gmail.com \
    --cc=mchehab@kernel.org \
    --cc=nicolas.dufresne@collabora.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