From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: Irui Wang <irui.wang@mediatek.com>, Rob Herring <robh@kernel.org>
Cc: Alexandre Courbot <acourbot@chromium.org>,
Tiffany Lin <tiffany.lin@mediatek.com>,
Andrew-CT Chen <andrew-ct.chen@mediatek.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Fritz Koenig <frkoenig@chromium.org>,
Tzung-Bi Shih <tzungbi@chromium.org>,
Maoguang Meng <maoguang.meng@mediatek.com>,
Longfei Wang <longfei.wang@mediatek.com>,
Yunfei Dong <yunfei.dong@mediatek.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
srv_heupstream@mediatek.com, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/5] dt-bindings: media: mtk-vcodec: Add dma-ranges property
Date: Thu, 29 Apr 2021 13:15:57 +0200 [thread overview]
Message-ID: <2b97b41c-d5d8-ac32-a9cf-c7bef09ed8ef@xs4all.nl> (raw)
In-Reply-To: <1614581129.14457.0.camel@mhfsdcap03>
Hi Rob,
On 01/03/2021 07:45, Irui Wang wrote:
> On Wed, 2021-02-10 at 16:53 -0600, Rob Herring wrote:
>> On Wed, Feb 03, 2021 at 04:37:48PM +0800, Irui Wang wrote:
>>> Adds dma-ranges property for DMA addresses translation.
>>>
>>> Signed-off-by: Irui Wang <irui.wang@mediatek.com>
>>> ---
>>> Documentation/devicetree/bindings/media/mediatek-vcodec.txt | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/media/mediatek-vcodec.txt b/Documentation/devicetree/bindings/media/mediatek-vcodec.txt
>>> index f85276e629bf..e4644f8caee9 100644
>>> --- a/Documentation/devicetree/bindings/media/mediatek-vcodec.txt
>>> +++ b/Documentation/devicetree/bindings/media/mediatek-vcodec.txt
>>> @@ -23,6 +23,8 @@ Required properties:
>>> - iommus : should point to the respective IOMMU block with master port as
>>> argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.txt
>>> for details.
>>> +- dma-ranges : describes how the physical address space of the IOMMU maps
>>> + to memory.
>>
>> dma-ranges is supposed to be in a bus/parent node.
> Dear Rob,
>
> The mt8192 iommu support 0~16GB iova. We separate it to four banks:
> 0~4G; 4G~8G; 8G~12G; 12G~16G.
>
> The "dma-ranges" could be used to adjust the bank we locate.
> If we don't set this property. The default range always is 0~4G.
>
> Here we don't have actual bus/parent concept here. And the iova
> requirement is for our HW. Thus put the property in our node.
>
> Is this OK? If this is ok for you, I will put this message in the commit
> message and binding in next version.
Can you answer Irui's question? Just a reminder...
Much appreciated!
Regards,
Hans
>
> Regards
>>
>>> One of the two following nodes:
>>> - mediatek,vpu : the node of the video processor unit, if using VPU.
>>> - mediatek,scp : the node of the SCP unit, if using SCP.
>>> --
>>> 2.25.1
>>>
>
next prev parent reply other threads:[~2021-04-29 11:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 8:37 [PATCH 0/5] Support H264 4K on MT8192 Irui Wang
2021-02-03 8:37 ` [PATCH 1/5] dt-bindings: media: mtk-vcodec: Add dma-ranges property Irui Wang
2021-02-10 22:53 ` Rob Herring
2021-03-01 6:45 ` Irui Wang
2021-04-29 11:15 ` Hans Verkuil [this message]
2021-05-17 7:51 ` Irui Wang
2021-02-03 8:37 ` [PATCH 2/5] media: mtk-vcodec: Support 4GB~8GB range iova space for venc Irui Wang
2021-02-03 8:37 ` [PATCH 3/5] dt-bindings: media: mtk-vcodec: Add binding for MT8192 VENC Irui Wang
2021-02-10 22:54 ` Rob Herring
2021-02-03 8:37 ` [PATCH 4/5] media: mtk-vcodec: Add MT8192 H264 venc driver Irui Wang
2021-02-03 8:37 ` [PATCH 5/5] media: mtk-vcodec: Support H264 4K encoding on MT8192 Irui Wang
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=2b97b41c-d5d8-ac32-a9cf-c7bef09ed8ef@xs4all.nl \
--to=hverkuil-cisco@xs4all.nl \
--cc=acourbot@chromium.org \
--cc=andrew-ct.chen@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=frkoenig@chromium.org \
--cc=irui.wang@mediatek.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=longfei.wang@mediatek.com \
--cc=maoguang.meng@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=tiffany.lin@mediatek.com \
--cc=tzungbi@chromium.org \
--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;
as well as URLs for NNTP newsgroup(s).