From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: "Chengci.Xu" <chengci.xu@mediatek.com>,
Yong Wu <yong.wu@mediatek.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v3 1/3] dt-bindings: memory: mediatek: Add mt8188 smi binding
Date: Thu, 28 Jul 2022 13:01:32 +0200 [thread overview]
Message-ID: <c6c649ab-d147-a5b0-f95f-71b0ab0e8344@collabora.com> (raw)
In-Reply-To: <20220727104541.7309-2-chengci.xu@mediatek.com>
Il 27/07/22 12:45, Chengci.Xu ha scritto:
> Add mt8188 smi supporting in the bindings.
>
> In mt8188, there are two smi-common HW, one is for vdo(video output),
> the other is for vpp(video processing pipe). They connect with different
> smi-larbs, then some setting(bus_sel) is different. Differentiate them
> with the compatible string.
>
> Something like this:
>
> IOMMU(VDO) IOMMU(VPP)
> | |
> SMI_COMMON_VDO SMI_COMMON_VPP
> ---------------- ----------------
> | | ... | | ...
> larb0 larb2 ... larb1 larb3 ...
>
> Signed-off-by: Chengci.Xu <chengci.xu@mediatek.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
next parent reply other threads:[~2022-07-28 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220727104541.7309-1-chengci.xu@mediatek.com>
[not found] ` <20220727104541.7309-2-chengci.xu@mediatek.com>
2022-07-28 11:01 ` AngeloGioacchino Del Regno [this message]
[not found] ` <20220727104541.7309-4-chengci.xu@mediatek.com>
2022-07-28 11:03 ` [PATCH v3 3/3] memory: mtk-smi: mt8188: Add SMI Support AngeloGioacchino Del Regno
[not found] ` <20220727104541.7309-3-chengci.xu@mediatek.com>
2022-07-28 11:11 ` [PATCH v3 2/3] memory: mtk-smi: Add enable IOMMU SMC command for MM master 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=c6c649ab-d147-a5b0-f95f-71b0ab0e8344@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=chengci.xu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=yong.wu@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).