mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno  <angelogioacchino.delregno@collabora.com>
To: Yong Wu <yong.wu@mediatek.com>, Joerg Roedel <joro@8bytes.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh+dt@kernel.org>
Cc: Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	nfraprado@collabora.com, linux-media@vger.kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
	iommu@lists.linux.dev, mingyuan.ma@mediatek.com,
	yf.wang@mediatek.com, jianjiao.zeng@mediatek.com,
	Yunfei Dong <yunfei.dong@mediatek.com>,
	kyrie wu <kyrie.wu@mediatek.corp-partner.google.com>,
	chengci.xu@mediatek.com, youlin.pei@mediatek.com,
	anan.sun@mediatek.com
Subject: Re: [PATCH v4 08/11] iommu/mediatek: Add a gap for the iova regions
Date: Wed, 15 Feb 2023 13:35:43 +0100	[thread overview]
Message-ID: <7e108286-4ada-fdf3-cabc-aa3ce61117a6@collabora.com> (raw)
In-Reply-To: <20230215062544.8677-9-yong.wu@mediatek.com>

Il 15/02/23 07:25, Yong Wu ha scritto:
> As the removed property in the vcodec dt-binding, the property is:
> dma-ranges = <0x1 0x0 0x0 0x40000000 0x0 0xfff00000>;
> 
> The length is 0xfff0_0000 rather than 0x1_0000_0000, this means it
> requires 1M as a gap. This is because the end address for some vcodec
> HW is (address + size). If the size is 4G, the end address may be
> 0x2_0000_0000, and the width for vcodec register only is 32, then the
> HW may get the ZERO address.
> 
> Currently the consumer's dma-ranges property doesn't work, IOMMU
> has to consider this case. Add a bigger gap(8M) for all the regions
> to avoid it.
> 
> Signed-off-by: Yong Wu <yong.wu@mediatek.com>
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> ---
> Hi AngeloGioacchino,
> I define a new macro for this, I think it is a small change, thus keep
> you R-b.
> Thanks.

Hello!
You added a nice comment to the new definition describing that there's a 8M gap,
so it's completely fine; you can keep my R-b on this one just fine!

Regards,
Angelo

  reply	other threads:[~2023-02-15 12:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15  6:25 [PATCH v4 00/11] Adjust the dma-ranges for MTK IOMMU Yong Wu
2023-02-15  6:25 ` [PATCH v4 01/11] dt-bindings: media: mediatek,vcodec: Remove dma-ranges property Yong Wu
2023-02-15  6:25 ` [PATCH v4 02/11] dt-bindings: media: mediatek,jpeg: " Yong Wu
2023-02-15  6:25 ` [PATCH v4 03/11] iommu/mediatek: Improve comment for the current region/bank Yong Wu
2023-02-15  6:25 ` [PATCH v4 04/11] iommu/mediatek: Get regionid from larb/port id Yong Wu
2023-02-15  6:25 ` [PATCH v4 05/11] iommu/mediatek: mt8192: Add iova_region_larb_msk Yong Wu
2023-02-15 12:33   ` AngeloGioacchino Del Regno
2023-02-16  5:27     ` Yong Wu (吴勇)
2023-02-15  6:25 ` [PATCH v4 06/11] iommu/mediatek: mt8195: " Yong Wu
2023-02-15 12:33   ` AngeloGioacchino Del Regno
2023-02-15  6:25 ` [PATCH v4 07/11] iommu/mediatek: mt8186: " Yong Wu
2023-02-15  6:25 ` [PATCH v4 08/11] iommu/mediatek: Add a gap for the iova regions Yong Wu
2023-02-15 12:35   ` AngeloGioacchino Del Regno [this message]
2023-02-15  6:25 ` [PATCH v4 09/11] arm64: dts: mt8195: Add dma-ranges for the parent "soc" node Yong Wu
2023-02-15  6:25 ` [PATCH v4 10/11] arm64: dts: mt8195: Remove the unnecessary dma-ranges Yong Wu
2023-02-15  6:25 ` [PATCH v4 11/11] arm64: dts: mt8186: Add dma-ranges for the parent "soc" node Yong Wu

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=7e108286-4ada-fdf3-cabc-aa3ce61117a6@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=anan.sun@mediatek.com \
    --cc=chengci.xu@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hverkuil@xs4all.nl \
    --cc=iommu@lists.linux.dev \
    --cc=jianjiao.zeng@mediatek.com \
    --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=mingyuan.ma@mediatek.com \
    --cc=nfraprado@collabora.com \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.org \
    --cc=yf.wang@mediatek.com \
    --cc=yong.wu@mediatek.com \
    --cc=youlin.pei@mediatek.com \
    --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

all inboxes | Powered by JetHome®