From: Rob Herring <robh@kernel.org>
To: Benjamin Gaignard <benjamin.gaignard@collabora.com>
Cc: will@kernel.org, devicetree@vger.kernel.org,
iommu@lists.linux-foundation.org, xxm@rock-chips.com,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel@collabora.com, linux-arm-kernel@lists.infradead.org,
joro@8bytes.org, robh+dt@kernel.org, heiko@sntech.de
Subject: Re: [PATCH v3 2/4] dt-bindings: iommu: rockchip: Add compatible for v2
Date: Thu, 6 May 2021 15:35:39 -0500 [thread overview]
Message-ID: <20210506203539.GA759432@robh.at.kernel.org> (raw)
In-Reply-To: <20210504084124.131884-3-benjamin.gaignard@collabora.com>
On Tue, 04 May 2021 10:41:22 +0200, Benjamin Gaignard wrote:
> Add compatible for the second version of IOMMU hardware block.
> RK356x IOMMU can also be link to a power domain.
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@collabora.com>
> ---
> version 3:
> - Rename compatible with SoC name
>
> version 2:
> - Add power-domains property
>
> .../devicetree/bindings/iommu/rockchip,iommu.yaml | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-05-06 20:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 8:41 [PATCH v3 0/4] Add driver for rk356x Benjamin Gaignard
2021-05-04 8:41 ` [PATCH v3 1/4] dt-bindings: iommu: rockchip: Convert IOMMU to DT schema Benjamin Gaignard
2021-05-06 20:35 ` Rob Herring
2021-05-04 8:41 ` [PATCH v3 2/4] dt-bindings: iommu: rockchip: Add compatible for v2 Benjamin Gaignard
2021-05-06 20:35 ` Rob Herring [this message]
2021-05-04 8:41 ` [PATCH v3 3/4] ARM: dts: rockchip: rk322x: Fix iommu-cells properties name Benjamin Gaignard
2021-05-04 8:41 ` [PATCH v3 4/4] iommu: rockchip: Add support iommu v2 Benjamin Gaignard
2021-05-07 15:35 ` Robin Murphy
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=20210506203539.GA759432@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=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).