From: Rob Herring <robh@kernel.org>
To: Dejia Shang <dejia.shang@armchina.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
toby.shang@armchina.com
Subject: Re: [PATCH 3/4] dt-bindings: add vendor-prefix and documentation for Zhouyi NPU
Date: Thu, 16 Dec 2021 09:29:30 -0600 [thread overview]
Message-ID: <YbtbWh2dhMhMHMfX@robh.at.kernel.org> (raw)
In-Reply-To: <20211215103609.9268-4-dejia.shang@armchina.com>
On Wed, Dec 15, 2021 at 06:36:08PM +0800, Dejia Shang wrote:
> To enable this NPU IP in Arm-Linux system, SoC vendors should
> write devicetree files as documented.
>
> Signed-off-by: Dejia Shang <dejia.shang@armchina.com>
> ---
> .../bindings/misc/armchina,zhouyi-npu.yaml | 57 +++++++++++++++++++
> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
> 2 files changed, 59 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/misc/armchina,zhouyi-npu.yaml
>
> diff --git a/Documentation/devicetree/bindings/misc/armchina,zhouyi-npu.yaml b/Documentation/devicetree/bindings/misc/armchina,zhouyi-npu.yaml
> new file mode 100644
> index 000000000000..d3fdea101114
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/misc/armchina,zhouyi-npu.yaml
> @@ -0,0 +1,57 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/misc/armchina,zhouyi-npu.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: ArmChina Zhouyi NPU bindings
> +
> +maintainers:
> + - Dejia Shang <dejia.shang@armchina.com>
> +
> +description: |
> + Armchina AI accelerator IP - Zhouyi NPU
> +
> +properties:
> + compatible:
> + items:
> + - const: armchina,zhouyi-v1
> + - const: armchina,zhouyi-v2
> + - const: armchina,zhouyi
This says compatible must be a list of all 3 of these.
Where do v1 and v2 come from? We don't do version numbers in DT usually
unless they correspond to h/w revision registers or h/w documentation. I
would assume the h/w follows the Arm rXpY form?
> +
> + reg:
> + maxItems: 1
> +
> + memory-region:
> + maxItems: 2
What is each region?
This requires 2 entries, but the example only has 1.
> +
> + interrupts:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> +
> + reserved-memory {
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + aipu_ddr_reserved: aipu-shmem@0xA0000000 {
aipu-shmem@a0000000
> + compatible = "shared-dma-pool";
> + no-map;
> + reg = <0x0 0xA0000000 0x0 0x4000000>;
> + };
> + };
> +
> + aipu0@0x64000000 {
Drop '0x'
> + compatible = "armchina,zhouyi";
> + reg = <0x0 0x64000000 0x0 0x1000>;
> + memory-region=<&aipu_ddr_reserved>;
> + interrupts = <0 168 1>;
> + };
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> index 66d6432fd781..4b1865d92455 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -123,6 +123,8 @@ patternProperties:
> description: ARM Ltd.
> "^armadeus,.*":
> description: ARMadeus Systems SARL
> + "^armchina,.*":
> + description: Arm Technology (China) Co., Ltd.
> "^arrow,.*":
> description: Arrow Electronics
> "^artesyn,.*":
> --
> 2.17.1
>
> IMPORTANT NOTICE: The contents of this email and any attachments may be privileged and confidential. If you are not the intended recipient, please delete the email immediately. It is strictly prohibited to disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ©Arm Technology (China) Co., Ltd copyright and reserve all rights. 重要提示:本邮件(包括任何附件)可能含有专供明确的个人或目的使用的机密信息,并受法律保护。如果您并非该收件人,请立即删除此邮件。严禁通过任何渠道,以任何目的,向任何人披露、储存或复制邮件信息或者据此采取任何行动。感谢您的配合。 ©安谋科技(中国)有限公司 版权所有并保留一切权利。
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-16 15:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 10:36 [PATCH 0/4] misc: add ArmChina Zhouyi NPU driver Dejia Shang
2021-12-15 10:36 ` [PATCH 2/4] Documentation: add sysfs entries for Zhouyi NPU Dejia Shang
2021-12-15 10:51 ` Greg KH
2021-12-15 10:36 ` [PATCH 3/4] dt-bindings: add vendor-prefix and documentation " Dejia Shang
2021-12-15 10:51 ` Greg KH
2021-12-16 15:29 ` Rob Herring [this message]
2021-12-17 6:57 ` Dejia Shang
2021-12-15 10:36 ` [PATCH 4/4] MAINTAINERS: add maintainer info. " Dejia Shang
2021-12-15 10:51 ` Greg KH
[not found] ` <20211215103609.9268-2-dejia.shang@armchina.com>
2021-12-15 10:50 ` [PATCH 1/4] misc: add ArmChina Zhouyi NPU driver Greg KH
2021-12-15 10:50 ` [PATCH 0/4] " Greg KH
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=YbtbWh2dhMhMHMfX@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=dejia.shang@armchina.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=toby.shang@armchina.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).