From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>
Cc: kernel@collabora.com, Arnd Bergmann <arnd@arndb.de>,
Bjorn Andersson <quic_bjorande@quicinc.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Shawn Guo <shawnguo@kernel.org>, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] arm64: defconfig: Enable DMA_RESTRICTED_POOL
Date: Wed, 1 Feb 2023 14:13:06 +0100 [thread overview]
Message-ID: <ea37d824-5bfa-9e6c-a007-c5b794cd44e3@collabora.com> (raw)
In-Reply-To: <20230130200820.82084-2-nfraprado@collabora.com>
Il 30/01/23 21:08, Nícolas F. R. A. Prado ha scritto:
> Enable support for restricted DMA pools which provide a level of DMA
> memory protection on systems with limited hardware protection
> capabilities, such as those lacking an IOMMU.
>
> For instance, mt8192-asurada-spherion makes use of this to provide a
> restricted DMA region for WiFi since its MT7921E WiFi card is connected
> through PCIe, and the MT8192 SoC doesn't have an IOMMU context for the
> PCIe controller.
>
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
>
On MT8173 Elm, MT8192 Spherion, MT8195 Tomato:
Tested-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
next prev parent reply other threads:[~2023-02-01 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 20:08 [PATCH v3 1/2] arm64: defconfig: Enable missing configs for mt8192-asurada Nícolas F. R. A. Prado
2023-01-30 20:08 ` [PATCH v3 2/2] arm64: defconfig: Enable DMA_RESTRICTED_POOL Nícolas F. R. A. Prado
2023-02-01 13:13 ` AngeloGioacchino Del Regno [this message]
2023-01-31 11:29 ` [PATCH v3 1/2] arm64: defconfig: Enable missing configs for mt8192-asurada 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=ea37d824-5bfa-9e6c-a007-c5b794cd44e3@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=geert+renesas@glider.be \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=matthias.bgg@gmail.com \
--cc=nfraprado@collabora.com \
--cc=quic_bjorande@quicinc.com \
--cc=shawnguo@kernel.org \
--cc=will@kernel.org \
/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®