From: Matthias Brugger <matthias.bgg@gmail.com>
To: Joerg Roedel <joro@8bytes.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: yong.wu@mediatek.com, will@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org,
iommu@lists.linux-foundation.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
krzysztof.kozlowski@linaro.org, miles.chen@mediatek.com
Subject: Re: [PATCH v4 0/5] mtk_iommu: Specify phandles to infracfg and pericfg
Date: Wed, 22 Jun 2022 16:12:47 +0200 [thread overview]
Message-ID: <4023cf19-601c-a2ba-85b0-450fb2df9401@gmail.com> (raw)
In-Reply-To: <YrMc2EUBDIxnoWiB@8bytes.org>
Hi Joerg,
On 22/06/2022 15:44, Joerg Roedel wrote:
> On Thu, Jun 16, 2022 at 01:08:25PM +0200, AngeloGioacchino Del Regno wrote:
>> AngeloGioacchino Del Regno (5):
>> dt-bindings: iommu: mediatek: Add mediatek,infracfg phandle
>> iommu/mediatek: Lookup phandle to retrieve syscon to infracfg
>> arm64: dts: mediatek: mt8173: Add mediatek,infracfg phandle for IOMMU
>> arm64: dts: mediatek: mt2712e: Add mediatek,infracfg phandle for IOMMU
>> iommu/mediatek: Cleanup pericfg lookup flow
>>
>> .../bindings/iommu/mediatek,iommu.yaml | 17 +++++++
>> arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 2 +
>> arch/arm64/boot/dts/mediatek/mt8173.dtsi | 1 +
>> drivers/iommu/mtk_iommu.c | 50 +++++++++++--------
>> 4 files changed, 49 insertions(+), 21 deletions(-)
>
> Applied, thanks.
I wanted to check if you took also 3 and 4, as these should go through my tree.
Unfortunately you haven't pushed your tree (yet). In case you took the whole
series, can you please drop the dts patches. I'll apply them now on my
v5.19-next/dts64 branch.
Regards.
Matthias
next prev parent reply other threads:[~2022-06-22 14:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 11:08 [PATCH v4 0/5] mtk_iommu: Specify phandles to infracfg and pericfg AngeloGioacchino Del Regno
2022-06-16 11:08 ` [PATCH v4 1/5] dt-bindings: iommu: mediatek: Add mediatek,infracfg phandle AngeloGioacchino Del Regno
2022-06-16 12:57 ` Matthias Brugger
2022-06-16 11:08 ` [PATCH v4 2/5] iommu/mediatek: Lookup phandle to retrieve syscon to infracfg AngeloGioacchino Del Regno
2022-06-16 11:08 ` [PATCH v4 3/5] arm64: dts: mediatek: mt8173: Add mediatek,infracfg phandle for IOMMU AngeloGioacchino Del Regno
2022-06-16 11:08 ` [PATCH v4 4/5] arm64: dts: mediatek: mt2712e: " AngeloGioacchino Del Regno
2022-06-16 11:08 ` [PATCH v4 5/5] iommu/mediatek: Cleanup pericfg lookup flow AngeloGioacchino Del Regno
2022-06-16 13:03 ` Matthias Brugger
2022-06-22 13:44 ` [PATCH v4 0/5] mtk_iommu: Specify phandles to infracfg and pericfg Joerg Roedel
2022-06-22 14:12 ` Matthias Brugger [this message]
2022-06-23 7:32 ` Joerg Roedel
2022-06-22 14:12 ` Matthias Brugger
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=4023cf19-601c-a2ba-85b0-450fb2df9401@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=krzysztof.kozlowski+dt@linaro.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=miles.chen@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=will@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).