From: Rob Herring <robh@kernel.org>
To: Chunyan Zhang <zhang.lyra@gmail.com>
Cc: Joerg Roedel <joro@8bytes.org>,
iommu@lists.linux-foundation.org, devicetree@vger.kernel.org,
Baolin Wang <baolin.wang7@gmail.com>,
linux-kernel@vger.kernel.org, Orson Zhai <orsonzhai@gmail.com>,
Sheng Xu <sheng.xu@unisoc.com>,
Kevin Tang <kevin.tang@unisoc.com>
Subject: Re: [RFC PATCH 1/2] dt-bindings: iommu: add bindings for sprd iommu
Date: Thu, 7 Jan 2021 19:25:45 -0700 [thread overview]
Message-ID: <20210108022545.GA1744725@robh.at.kernel.org> (raw)
In-Reply-To: <20201223111633.1711477-1-zhang.lyra@gmail.com>
On Wed, Dec 23, 2020 at 07:16:32PM +0800, Chunyan Zhang wrote:
> From: Chunyan Zhang <chunyan.zhang@unisoc.com>
>
> This patch only adds bindings to support display iommu, support for others
> would be added once finished tests with those devices, such as Image
> codec(jpeg) processor, a few signal processors, including VSP(video),
> GSP(graphic), ISP(image), and camera CPP, etc.
>
> Signed-off-by: Chunyan Zhang <chunyan.zhang@unisoc.com>
> ---
> .../devicetree/bindings/iommu/sprd,iommu.yaml | 44 +++++++++++++++++++
> 1 file changed, 44 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iommu/sprd,iommu.yaml
>
> diff --git a/Documentation/devicetree/bindings/iommu/sprd,iommu.yaml b/Documentation/devicetree/bindings/iommu/sprd,iommu.yaml
> new file mode 100644
> index 000000000000..4d9a578a7cc9
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iommu/sprd,iommu.yaml
> @@ -0,0 +1,44 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +# Copyright 2020 Unisoc Inc.
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iommu/sprd,iommu.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Unisoc IOMMU and Multi-media MMU
> +
> +maintainers:
> + - Chunyan Zhang <zhang.lyra@gmail.com>
> +
> +properties:
> + compatible:
> + enum:
> + - sprd,iommu-disp
Needs to be Soc specific. Is this block specific to display subsys or
that just happens to be where the instance is?
> +
> + reg:
> + maxItems: 1
> +
> + "#iommu-cells":
> + const: 0
> + description:
> + Unisoc IOMMUs are all single-master IOMMU devices, therefore no
> + additional information needs to associate with its master device.
> + Please refer to the generic bindings document for more details,
> + Documentation/devicetree/bindings/iommu/iommu.txt
> +
> +required:
> + - compatible
> + - reg
> + - "#iommu-cells"
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + iommu_disp: iommu@63000000 {
> + compatible = "sprd,iommu-disp";
> + reg = <0x63000000 0x880>;
> + #iommu-cells = <0>;
> + };
> +
> +...
> --
> 2.25.1
>
next prev parent reply other threads:[~2021-01-08 2:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 11:16 [RFC PATCH 1/2] dt-bindings: iommu: add bindings for sprd iommu Chunyan Zhang
2020-12-23 11:16 ` [RFC PATCH 2/2] iommu: add Unisoc iommu basic driver Chunyan Zhang
2021-01-08 2:25 ` Rob Herring [this message]
2021-01-08 11:33 ` [RFC PATCH 1/2] dt-bindings: iommu: add bindings for sprd iommu Chunyan Zhang
2021-01-13 13:47 ` Rob Herring
2021-01-21 7:51 ` Chunyan Zhang
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=20210108022545.GA1744725@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=baolin.wang7@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kevin.tang@unisoc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=sheng.xu@unisoc.com \
--cc=zhang.lyra@gmail.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).