public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "Yunfei Dong (董云飞)" <Yunfei.Dong@mediatek.com>
To: "linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"nhebert@chromium.org" <nhebert@chromium.org>,
	"nicolas.frattaroli@collabora.com"
	<nicolas.frattaroli@collabora.com>,
	"nicolas.dufresne@collabora.com" <nicolas.dufresne@collabora.com>,
	"daniel.almeida@collabora.com" <daniel.almeida@collabora.com>,
	"benjamin.gaignard@collabora.com"
	<benjamin.gaignard@collabora.com>,
	"sebastian.fricke@collabora.com" <sebastian.fricke@collabora.com>,
	"hverkuil-cisco@xs4all.nl" <hverkuil-cisco@xs4all.nl>,
	"AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>,
	Nicolas Prado <nfraprado@collabora.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"frkoenig@chromium.org" <frkoenig@chromium.org>,
	"stevecho@chromium.org" <stevecho@chromium.org>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"daniel@ffwll.ch" <daniel@ffwll.ch>,
	Project_Global_Chrome_Upstream_Group
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	"hsinyi@chromium.org" <hsinyi@chromium.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 02/14] media: mediatek: vcodec: add decoder compatible to support mt8196
Date: Mon, 23 Mar 2026 02:06:26 +0000	[thread overview]
Message-ID: <93a8cba5d58c9485bccf7fa9605ce715205b559d.camel@mediatek.com> (raw)
In-Reply-To: <996341171629763ec9ecc0db6da61319ee99a970.camel@collabora.com>

Hi Nicolas,

Thanks for your suggestion.

On Thu, 2026-03-19 at 16:03 -0400, Nicolas Dufresne wrote:
> Le vendredi 13 février 2026 à 02:13 +0000, Yunfei Dong (董云飞) a
> écrit :
> > I had already confirmed with kyrie, he had changed the compatible
> > patch
> > in mt8189's patch set. So I just need to add mt8196's compatible.
> > 
> > 
> > 
https://patchwork.linuxtv.org/project/linux-media/patch/20260127024248.18406-3-kyrie.wu@mediatek.com/
> > 
> > mt8189's patch set is based on this patch set(8196's).
> 
> I will ask to work the other way around. Kiril patchset is very close
> to be
> ready, and once in, you should be able to rebase on top.
> 
> Note that this patch is miss-ordered, you should implement all the
> VCP/firmware
> part before you modify the probe function.
> 

Kyrie's patchset is close to be merged, but mt8189 need to depend on
mt8196's change. We don't want to break the dependency currently.

Could
you please help to review other patches, I will reply in time as soon
as possible.

About the order to probe function, I will change it in next version.

Best Regards,
Yunfei Dong

> regards,
> Nicolas

  reply	other threads:[~2026-03-23  2:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11  5:41 [PATCH v3 00/14] media: mediatek: vcodec: support video decoder in mt8196 Yunfei Dong
2026-02-11  5:41 ` [PATCH v3 01/14] dt-bindings: media: mediatek: vcodec: add decoder dt-bindings for mt8196 Yunfei Dong
2026-02-11  6:33   ` Krzysztof Kozlowski
2026-02-11  5:41 ` [PATCH v3 02/14] media: mediatek: vcodec: add decoder compatible to support mt8196 Yunfei Dong
2026-02-12 16:48   ` Nicolas Frattaroli
2026-02-12 19:31     ` Nicolas Dufresne
2026-02-13  2:13       ` Yunfei Dong (董云飞)
2026-03-19 20:03         ` Nicolas Dufresne
2026-03-23  2:06           ` Yunfei Dong (董云飞) [this message]
2026-02-11  5:41 ` [PATCH v3 03/14] media: mediatek: vcodec: add driver to support vcp Yunfei Dong
2026-02-11  5:41 ` [PATCH v3 04/14] media: mediatek: vcodec: add driver to support vcp encoder Yunfei Dong
2026-02-11  5:41 ` [PATCH v3 05/14] media: mediatek: vcodec: get different firmware ipi id Yunfei Dong
2026-02-11  5:41 ` [PATCH v3 06/14] media: mediatek: vcodec: get share memory address Yunfei Dong
2026-02-11  5:41 ` [PATCH v3 07/14] media: mediatek: vcodec: define MT8196 vcodec levels Yunfei Dong
2026-02-11  5:41 ` [PATCH v3 08/14] media: mediatek: vcodec: support vcp architecture Yunfei Dong
2026-02-11  5:41 ` [PATCH v3 09/14] media: mediatek: vcodec: support 36bit iova address Yunfei Dong
2026-02-11  5:41 ` [PATCH v3 10/14] media: mediatek: vcodec: clean xpc status Yunfei Dong
2026-02-11  5:41 ` [PATCH v3 11/14] media: mediatek: vcodec: add debug information Yunfei Dong
2026-02-11  5:41 ` [PATCH v3 12/14] media: mediatek: vcodec: send share memory address to vcp Yunfei Dong
2026-02-11  5:41 ` [PATCH v3 13/14] media: mediatek: decoder: fill av1 buffer size with picinfo Yunfei Dong
2026-02-11  5:41 ` [PATCH v3 14/14] media: mediatek: decoder: support av1 extend vsi 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=93a8cba5d58c9485bccf7fa9605ce715205b559d.camel@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=nicolas.frattaroli@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