public inbox for linux-mediatek@lists.infradead.org
 help / color / mirror / Atom feed
From: "Yong Wu (吴勇)" <Yong.Wu@mediatek.com>
To: "joro@8bytes.org" <joro@8bytes.org>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"mchehab@kernel.org" <mchehab@kernel.org>,
	"angelogioacchino.delregno@collabora.com"
	<angelogioacchino.delregno@collabora.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>
Cc: "linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Youlin Pei (裴友林)" <youlin.pei@mediatek.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Anan Sun (孙安安)" <Anan.Sun@mediatek.com>,
	"Libo Kang (康利波)" <Libo.Kang@mediatek.com>,
	"kyrie.wu@mediatek.corp-partner.google.com"
	<kyrie.wu@mediatek.corp-partner.google.com>,
	"robin.murphy@arm.com" <robin.murphy@arm.com>,
	"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
	"Chengci Xu (许承赐)" <Chengci.Xu@mediatek.com>,
	"Yunfei Dong (董云飞)" <Yunfei.Dong@mediatek.com>,
	"YF Wang (王云飞)" <YF.Wang@mediatek.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"krzysztof.kozlowski+dt@linaro.org"
	<krzysztof.kozlowski+dt@linaro.org>,
	"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
	"Mingyuan Ma (马鸣远)" <Mingyuan.Ma@mediatek.com>,
	"will@kernel.org" <will@kernel.org>,
	"nfraprado@collabora.com" <nfraprado@collabora.com>
Subject: Re: [PATCH 07/10] iommu/mediatek: Add a gap for the iova regions
Date: Tue, 17 Jan 2023 02:53:11 +0000	[thread overview]
Message-ID: <fc4be21af5408832f3b92927a1aeb57ebc1f8a01.camel@mediatek.com> (raw)
In-Reply-To: <1a9a09d5-58e2-badc-6d1c-fe2008c305f9@collabora.com>

On Mon, 2023-01-16 at 10:46 +0100, AngeloGioacchino Del Regno wrote:
> Il 13/01/23 07:01, Yong Wu ha scritto:
> > Currenly masters can not indicate its special dma-ranges. Prepare
> > for vcodec. some vcodec end address is address + size, if our size
> > is 4G, the end address may be 0x2_0000_0000. and the
> > register is u32, then it may get zero. thus add a gap(8M) for
> > all the regions.
> > 
> > Signed-off-by: Yong Wu <yong.wu@mediatek.com>
> 
> I definitely agree on the fact that we do *need* this series... 

Thanks very much for your review.

> but this particular commit looks like a hack.
> 
> I'm not convinced: I have a hunch that this one will sooner or later
> backfire
> on us and break things again... at the same time, I'm not sure how to
> do this
> properly at this point (I didn't do any research, anyway).

I got a real vcodec issue described in the commit message. As you may
see in the vcodec's dt-binding example[1/10] or the dts node[9/10],
their length is 0xfff00000 that means they use 1M as the gap. Vcodec
use this for a long time. After this patchset, this property is unused,
then I have to take care of this in the iommu, therefore this patch is
required, and I just give a bigger gap(8M) here.

> 
> Ideas?
> 
> Regards,
> Angelo
> 

  reply	other threads:[~2023-01-17  2:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13  6:01 [PATCH 00/10] Adjust the dma-ranges for MTK IOMMU Yong Wu
2023-01-13  6:01 ` [PATCH 01/10] dt-bindings: media: mediatek,vcodec: Remove dma-ranges property Yong Wu
2023-01-13  8:25   ` Krzysztof Kozlowski
2023-01-16  8:01     ` Yong Wu (吴勇)
2023-01-16  8:06       ` Krzysztof Kozlowski
2023-01-16  9:16         ` Yong Wu (吴勇)
2023-01-17 10:44           ` Krzysztof Kozlowski
2023-01-16  9:47   ` AngeloGioacchino Del Regno
2023-01-13  6:01 ` [PATCH 02/10] dt-bindings: media: mediatek,jpeg: " Yong Wu
2023-01-16  9:47   ` AngeloGioacchino Del Regno
2023-01-13  6:01 ` [PATCH 03/10] iommu/mediatek: Get regionid from larb/port id Yong Wu
2023-01-13  6:01 ` [PATCH 04/10] iommu/mediatek: mt8195: Add larb_region_msk Yong Wu
2023-01-13  6:01 ` [PATCH 05/10] iommu/mediatek: mt8186: add larb_region_msk Yong Wu
2023-01-13  6:01 ` [PATCH 06/10] iommu/mediatek: mt8192: " Yong Wu
2023-01-13  6:01 ` [PATCH 07/10] iommu/mediatek: Add a gap for the iova regions Yong Wu
2023-01-16  9:46   ` AngeloGioacchino Del Regno
2023-01-17  2:53     ` Yong Wu (吴勇) [this message]
2023-02-14  5:33     ` Yong Wu (吴勇)
2023-01-13  6:01 ` [PATCH 08/10] arm64: dts: mt8195: Add dma-ranges for the parent "soc" node Yong Wu
2023-01-16  9:47   ` AngeloGioacchino Del Regno
2023-01-13  6:01 ` [PATCH 09/10] arm64: dts: mt8195: Remove the unnecessary dma-ranges Yong Wu
2023-01-16  9:47   ` AngeloGioacchino Del Regno
2023-01-13  6:01 ` [PATCH 10/10] arm64: dts: mt8186: Add dma-ranges for the parent "soc" node Yong Wu
2023-01-16  9:47   ` AngeloGioacchino Del Regno

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=fc4be21af5408832f3b92927a1aeb57ebc1f8a01.camel@mediatek.com \
    --to=yong.wu@mediatek.com \
    --cc=Anan.Sun@mediatek.com \
    --cc=Chengci.Xu@mediatek.com \
    --cc=Libo.Kang@mediatek.com \
    --cc=Mingyuan.Ma@mediatek.com \
    --cc=YF.Wang@mediatek.com \
    --cc=Yunfei.Dong@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hverkuil@xs4all.nl \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kyrie.wu@mediatek.corp-partner.google.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=matthias.bgg@gmail.com \
    --cc=mchehab@kernel.org \
    --cc=nfraprado@collabora.com \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.org \
    --cc=youlin.pei@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