From: Sven Peter <sven@kernel.org>
To: Janne Grunau <j@jannau.net>, Neal Gompa <neal@gompa.dev>,
"Joerg Roedel (AMD)" <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
iommu@lists.linux.dev, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Hector Martin <marcan@marcan.st>
Subject: Re: [PATCH v2 2/2] iommu: apple-dart: Support specifying the DMA aperture in the DT
Date: Tue, 1 Sep 2026 22:45:52 +0200 [thread overview]
Message-ID: <2b95fa20-22a5-4ef2-9ea6-c6fb7d1f16ac@kernel.org> (raw)
In-Reply-To: <20260831-iommu-apple-dart-aperture-v2-2-d16ce3770299@jannau.net>
Hi,
On 8/31/26 15:46, Janne Grunau wrote:
> Apple DARTs are often connected directly to devices that expect only a
> portion of their address space to be used for DMA (for example, because
> other ranges are mapped directly to something else). Devices can specify
> the start and end of the aperture via "iommus" args if the DART device
> node specifies "#iommu-cells = <5>. Aperture start and length are 64-bit
> values as apertures above and larger than 4GB are used.
> Limit compile testing to 64-bit architectures to avoid warnings in the
> calculation of 64-bit dma_addr_t values.
I don't see any Kconfig hunk below, did you drop it by accident?
Otherwise:
Reviewed-by: Sven Peter <sven@kernel.org>
Sven
next prev parent reply other threads:[~2026-09-01 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 13:46 [PATCH v2 0/2] iommu: apple-dart: device specific DMA aperture support Janne Grunau
2026-08-31 13:46 ` [PATCH v2 1/2] dt-bindings: iommu: dart: Support specifying the DMA aperture Janne Grunau
2026-08-31 13:46 ` [PATCH v2 2/2] iommu: apple-dart: Support specifying the DMA aperture in the DT Janne Grunau
2026-08-31 16:29 ` sashiko-bot
2026-09-01 20:45 ` Sven Peter [this message]
2026-09-02 19:17 ` Janne Grunau
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=2b95fa20-22a5-4ef2-9ea6-c6fb7d1f16ac@kernel.org \
--to=sven@kernel.org \
--cc=asahi@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=j@jannau.net \
--cc=joro@8bytes.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=neal@gompa.dev \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.