devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yunfei Dong (董云飞)" <Yunfei.Dong@mediatek.com>
To: "wenst@chromium.org" <wenst@chromium.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"frkoenig@chromium.org" <frkoenig@chromium.org>,
	"stevecho@chromium.org" <stevecho@chromium.org>,
	"nhebert@chromium.org" <nhebert@chromium.org>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"nicolas.dufresne@collabora.com" <nicolas.dufresne@collabora.com>,
	"daniel.almeida@collabora.com" <daniel.almeida@collabora.com>,
	"daniel@ffwll.ch" <daniel@ffwll.ch>,
	Project_Global_Chrome_Upstream_Group
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	"benjamin.gaignard@collabora.com"
	<benjamin.gaignard@collabora.com>,
	"sebastian.fricke@collabora.com" <sebastian.fricke@collabora.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"hverkuil-cisco@xs4all.nl" <hverkuil-cisco@xs4all.nl>,
	"hsinyi@chromium.org" <hsinyi@chromium.org>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	"Nicolas Prado" <nfraprado@collabora.com>
Subject: Re: [PATCH 0/6] media: mediatek: vcodec: support h264 extend vsi
Date: Wed, 16 Oct 2024 03:44:34 +0000	[thread overview]
Message-ID: <c320a54c290827372a6c4fc18b89a4c702917175.camel@mediatek.com> (raw)
In-Reply-To: <CAGXv+5HV5EPvhFb6oFkRBSw-EGaccxDGBrW0tVDoWQR0RAAeiQ@mail.gmail.com>

Hi Chen-Yu,

Thanks for your help to review the patch.
On Tue, 2024-10-15 at 15:54 +0800, Chen-Yu Tsai wrote:
>  	 
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
>  Hi,
> 
> On Mon, Oct 14, 2024 at 3:33 PM Yunfei Dong <yunfei.dong@mediatek.com
> > wrote:
> >
> > The working buffer address start and end are calculated in kernel
> > side currently, can't calculate the address end if the driver only
> > getting the address file handle, not the real physical address.
> Need
> > to extend the vsi to calculate the address end in scp.
> >
> > Re-construct some interface and add config to support extend and
> non
> > extend at the same time.
> > ---
> > This patch series depends on:
> > [1] 
> https://patchwork.kernel.org/project/linux-mediatek/cover/20241012064333.27269-1-yunfei.dong@mediatek.com
> > ---
> > Yunfei Dong (6):
> >   media: mediatek: vcodec: extend h264 video share information
> >   media: mediatek: vcodec: remove parse nal info in kernel
> >   media: mediatek: vcodec: remove vsi operation in common interface
> >   media: mediatek: vcodec: rename vsi to extend vsi
> >   media: mediatek: vcodec: adding non extend struct
> >   media: mediatek: vcodec: support extend h264 driver
> 
> This should be reworked so that "adding non extend struct" is not
> needed.
> "rename vsi to extend vsi" and "extend h264 video share information"
> could be combined so that you are "adding" the extended data
> structures,
> not reworking the existing ones. Otherwise the whole thing breaks
> existing
> systems until "adding non extend struct" is applied, making the
> series
> non-bisectable.
> 
> 
Your advice is very reasonable, I will rewrite the patches again.

> ChenYu
> 
Best Regards,
Yunfei Dong
> >
> >  .../vcodec/decoder/mtk_vcodec_dec_drv.h       |   2 +
> >  .../decoder/vdec/vdec_h264_req_multi_if.c     | 516
> +++++++++++++++++-
> >  2 files changed, 493 insertions(+), 25 deletions(-)
> >
> > --
> > 2.46.0
> >
> >

      reply	other threads:[~2024-10-16  3:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14  7:33 [PATCH 0/6] media: mediatek: vcodec: support h264 extend vsi Yunfei Dong
2024-10-14  7:33 ` [PATCH 1/6] media: mediatek: vcodec: extend h264 video share information Yunfei Dong
2024-10-14  7:33 ` [PATCH 2/6] media: mediatek: vcodec: remove parse nal info in kernel Yunfei Dong
2024-10-15  7:58   ` Chen-Yu Tsai
2024-10-16  3:46     ` Yunfei Dong (董云飞)
2024-10-14  7:33 ` [PATCH 3/6] media: mediatek: vcodec: remove vsi operation in common interface Yunfei Dong
2024-10-14  7:33 ` [PATCH 4/6] media: mediatek: vcodec: rename vsi to extend vsi Yunfei Dong
2024-10-14  7:33 ` [PATCH 5/6] media: mediatek: vcodec: adding non extend struct Yunfei Dong
2024-10-14  7:33 ` [PATCH 6/6] media: mediatek: vcodec: support extend h264 driver Yunfei Dong
2024-10-15  7:54 ` [PATCH 0/6] media: mediatek: vcodec: support h264 extend vsi Chen-Yu Tsai
2024-10-16  3:44   ` Yunfei Dong (董云飞) [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=c320a54c290827372a6c4fc18b89a4c702917175.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=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;
as well as URLs for NNTP newsgroup(s).