From: Benjamin Gaignard <benjamin.gaignard@collabora.com>
To: joro@8bytes.org, will@kernel.org, robh+dt@kernel.org,
heiko@sntech.de, xxm@rock-chips.com
Cc: iommu@lists.linux-foundation.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel@collabora.com,
Benjamin Gaignard <benjamin.gaignard@collabora.com>
Subject: [PATCH v4 0/6] Add IOMMU driver for rk356x
Date: Fri, 7 May 2021 11:02:26 +0200 [thread overview]
Message-ID: <20210507090232.233049-1-benjamin.gaignard@collabora.com> (raw)
This series adds the IOMMU driver for rk356x SoC.
Since a new compatible is needed to distinguish this second version of
IOMMU hardware block from the first one, it is an opportunity to convert
the binding to DT schema.
version 4:
- Add description for reg items
- Remove useless interrupt-names properties
- Add description for interrupts items
- Remove interrupt-names properties from DST files
version 3:
- Rename compatible with soc prefix
- Rebase on v5.12 tag
version 2:
- Fix iommu-cells typo in rk322x.dtsi
- Change maintainer
- Change reg maxItems
- Add power-domains property
Benjamin Gaignard (5):
dt-bindings: iommu: rockchip: Convert IOMMU to DT schema
dt-bindings: iommu: rockchip: Add compatible for v2
ARM: dts: rockchip: rk322x: Fix IOMMU nodes properties
ARM: dts: rockchip: rk3036: Remove useless interrupt-names on IOMMU
node
ARM64: dts: rockchip: rk3036: Remove useless interrupt-names
properties
Simon Xue (1):
iommu: rockchip: Add support iommu v2
.../bindings/iommu/rockchip,iommu.txt | 38 --
.../bindings/iommu/rockchip,iommu.yaml | 85 ++++
arch/arm/boot/dts/rk3036.dtsi | 1 -
arch/arm/boot/dts/rk322x.dtsi | 10 +-
arch/arm64/boot/dts/rockchip/px30.dtsi | 2 -
drivers/iommu/rockchip-iommu.c | 422 +++++++++++++++++-
6 files changed, 494 insertions(+), 64 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/iommu/rockchip,iommu.txt
create mode 100644 Documentation/devicetree/bindings/iommu/rockchip,iommu.yaml
--
2.25.1
next reply other threads:[~2021-05-07 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 9:02 Benjamin Gaignard [this message]
2021-05-07 9:02 ` [PATCH v4 1/6] dt-bindings: iommu: rockchip: Convert IOMMU to DT schema Benjamin Gaignard
2021-05-07 20:15 ` Rob Herring
2021-05-07 9:02 ` [PATCH v4 2/6] dt-bindings: iommu: rockchip: Add compatible for v2 Benjamin Gaignard
2021-05-07 9:02 ` [PATCH v4 3/6] ARM: dts: rockchip: rk322x: Fix IOMMU nodes properties Benjamin Gaignard
2021-05-07 9:02 ` [PATCH v4 4/6] ARM: dts: rockchip: rk3036: Remove useless interrupt-names on IOMMU node Benjamin Gaignard
2021-05-07 9:02 ` [PATCH v4 5/6] ARM64: dts: rockchip: rk3036: Remove useless interrupt-names properties Benjamin Gaignard
2021-05-07 9:02 ` [PATCH v4 6/6] iommu: rockchip: Add support iommu v2 Benjamin Gaignard
2021-05-17 12:16 ` Heiko Stübner
2021-05-10 0:12 ` (subset) [PATCH v4 0/6] Add IOMMU driver for rk356x Heiko Stuebner
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=20210507090232.233049-1-benjamin.gaignard@collabora.com \
--to=benjamin.gaignard@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=will@kernel.org \
--cc=xxm@rock-chips.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).