From: Alexandre Mergnat <amergnat@baylibre.com>
To: Alexandre Bailon <abailon@baylibre.com>,
yong.wu@mediatek.com, joro@8bytes.org, will@kernel.org
Cc: robin.murphy@arm.com, matthias.bgg@gmail.com,
krzysztof.kozlowski@linaro.org, robh+dt@kernel.org,
iommu@lists.linux.dev, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/3] iommu: mediatek: Add support of unmanaged iommu domain
Date: Mon, 30 Jan 2023 13:04:00 +0100 [thread overview]
Message-ID: <30201eff-0339-da85-cf01-d0001af0d03f@baylibre.com> (raw)
In-Reply-To: <20230130102722.133271-3-abailon@baylibre.com>
On 30/01/2023 11:27, Alexandre Bailon wrote:
> Currently, the driver can allocate an unmanaged iommu domain.
> But, this only works for SoC having multiple bank or multiple iova region.
> This updates the driver to also support unmanaged iommu domain if
> MTK_UNMANAGED_DEVICE is set in the iommu id.
>
> Signed-off-by: Alexandre Bailon <abailon@baylibre.com>
Reviewed-by: Alexandre Mergnat <amergnat@baylibre.com>
next prev parent reply other threads:[~2023-01-30 12:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 10:27 [PATCH 0/3] Add support of unmanaged domain to mediatek IOMMU Alexandre Bailon
2023-01-30 10:27 ` [PATCH 1/3] dt-bindings: memory: mediatek: Add support of unmanaged iommu domain Alexandre Bailon
2023-01-30 11:57 ` Alexandre Mergnat
2023-01-30 11:58 ` Robin Murphy
2023-01-30 10:27 ` [PATCH 2/3] iommu: " Alexandre Bailon
2023-01-30 12:04 ` Alexandre Mergnat [this message]
2023-01-30 12:04 ` Robin Murphy
2023-01-31 13:08 ` Alexandre Bailon
2023-01-31 14:15 ` Robin Murphy
2023-01-31 15:31 ` Alexandre Bailon
2023-02-14 5:48 ` Yong Wu (吴勇)
2023-09-14 8:07 ` Alexandre Bailon
2023-09-14 14:19 ` Robin Murphy
2023-01-30 10:27 ` [PATCH 3/3] dt-bindings: iommu: memory: Use unmanaged iommu domain for the APU Alexandre Bailon
2023-01-30 12:04 ` Alexandre Mergnat
2023-01-30 22:50 ` Rob Herring
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=30201eff-0339-da85-cf01-d0001af0d03f@baylibre.com \
--to=amergnat@baylibre.com \
--cc=abailon@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.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=robin.murphy@arm.com \
--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).