From: Sven Peter <sven@svenpeter.dev>
To: Hector Martin <marcan@marcan.st>, Sven Peter <sven@svenpeter.dev>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Alyssa Rosenzweig <alyssa@rosenzweig.io>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org, asahi@lists.linux.dev,
iommu@lists.linux.dev, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/3] Apple M1 USB4/Thunderbolt DART support
Date: Sat, 11 Mar 2023 14:38:53 +0100 [thread overview]
Message-ID: <20230311133856.63840-1-sven@svenpeter.dev> (raw)
Hi,
The M1 SoCs have a second slightly different variant of the regular
DART used for the USB4 PCIe ports. It supports 64 instead of 16 streams
which requires a minor change to the MMIO layout.
There seems to be no way to tell them apart from the regular DARTs by
just looking at the DART_PARAMs register so we have to add a new
compatible for those.
Changes since v2:
- drop the manual bypass disable
- added Rob's tag
Changes since v1:
- apple,t8103-usb4-dart instead of apple,t8103-dart-usb4 as the
compatible
- collected Hector's tags
Best,
Sven
Sven Peter (3):
dt-bindings: iommu: dart: Add t8103-usb4-dart compatible
iommu: dart: Write to all DART_T8020_STREAM_SELECT
iommu: dart: Add support for t8103 USB4 DART
.../devicetree/bindings/iommu/apple,dart.yaml | 1 +
drivers/iommu/apple-dart.c | 35 +++++++++++++++++--
2 files changed, 34 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2023-03-11 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 13:38 Sven Peter [this message]
2023-03-11 13:38 ` [PATCH v3 1/3] dt-bindings: iommu: dart: Add t8103-usb4-dart compatible Sven Peter
2023-03-11 13:52 ` Mark Kettenis
2023-03-11 13:38 ` [PATCH v3 2/3] iommu: dart: Write to all DART_T8020_STREAM_SELECT Sven Peter
2023-03-11 13:38 ` [PATCH v3 3/3] iommu: dart: Add support for t8103 USB4 DART Sven Peter
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=20230311133856.63840-1-sven@svenpeter.dev \
--to=sven@svenpeter.dev \
--cc=alyssa@rosenzweig.io \
--cc=asahi@lists.linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=robh+dt@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 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).