From: Conor Dooley <conor@kernel.org>
To: Yixun Lan <dlan@gentoo.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Samuel Holland <samuel.holland@sifive.com>,
Anup Patel <anup@brainfault.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Lubomir Rintel <lkundrak@v3.sk>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Palmer Dabbelt <palmer@sifive.com>,
linux-riscv@lists.infradead.org, linux-serial@vger.kernel.org,
Inochi Amaoto <inochiama@outlook.com>,
Meng Zhang <zhangmeng.kevin@spacemit.com>,
Yangyu Chen <cyy@cyyself.name>
Subject: Re: [PATCH v2 03/10] dt-bindings: riscv: add SpacemiT K1 bindings
Date: Mon, 1 Jul 2024 13:24:20 +0100 [thread overview]
Message-ID: <20240701-undercook-flatterer-7f18f7420a6d@spud> (raw)
In-Reply-To: <20240627-k1-01-basic-dt-v2-3-cc06c7555f07@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]
On Thu, Jun 27, 2024 at 03:31:17PM +0000, Yixun Lan wrote:
> From: Yangyu Chen <cyy@cyyself.name>
>
> Add DT binding documentation for the SpacemiT K1 Soc[1] and the Banana
> Pi BPi-F3 board[2] which used it.
>
> [1] https://www.spacemit.com/en/spacemit-key-stone-2/
> [2] https://docs.banana-pi.org/en/BPI-F3/BananaPi_BPI-F3
>
Please make these link tags when you resend, like
Link: https://foo [1]
and don't leave blank lines between them and the signoff.
> Signed-off-by: Yangyu Chen <cyy@cyyself.name>
> Signed-off-by: Yixun Lan <dlan@gentoo.org>
> ---
> .../devicetree/bindings/riscv/spacemit.yaml | 24 ++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/riscv/spacemit.yaml b/Documentation/devicetree/bindings/riscv/spacemit.yaml
> new file mode 100644
> index 0000000000000..3b151fd02473e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/riscv/spacemit.yaml
> @@ -0,0 +1,24 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/riscv/spacemit.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: SpacemiT SoC-based boards
> +
> +description:
> + SpacemiT SoC-based boards
Please work out who is gonna maintain these SoCs and add that here to
resolve the bot's report.
Thanls,
Conor.
> +
> +properties:
> + $nodename:
> + const: '/'
> + compatible:
> + oneOf:
> + - items:
> + - enum:
> + - bananapi,bpi-f3
> + - const: spacemit,k1
> +
> +additionalProperties: true
> +
> +...
>
> --
> 2.45.2
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-07-01 12:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 15:31 [PATCH v2 00/10] riscv: add initial support for SpacemiT K1 Yixun Lan
2024-06-27 15:31 ` [PATCH v2 01/10] dt-bindings: vendor-prefixes: add spacemit Yixun Lan
2024-06-28 7:32 ` Krzysztof Kozlowski
2024-06-27 15:31 ` [PATCH v2 02/10] dt-bindings: riscv: Add SpacemiT X60 compatibles Yixun Lan
2024-07-01 12:25 ` Conor Dooley
2024-06-27 15:31 ` [PATCH v2 03/10] dt-bindings: riscv: add SpacemiT K1 bindings Yixun Lan
2024-06-27 18:00 ` Rob Herring (Arm)
2024-06-28 7:34 ` Krzysztof Kozlowski
2024-06-28 8:44 ` Yixun Lan
2024-07-01 12:24 ` Conor Dooley [this message]
2024-07-02 9:42 ` Yixun Lan
2024-06-27 15:31 ` [PATCH v2 04/10] dt-bindings: timer: Add SpacemiT K1 CLINT Yixun Lan
2024-07-01 12:22 ` Conor Dooley
2024-06-27 15:31 ` [PATCH v2 05/10] dt-bindings: interrupt-controller: Add SpacemiT K1 PLIC Yixun Lan
2024-06-27 15:31 ` [PATCH v2 06/10] dt-bindings: serial: 8250: Add SpacemiT K1 uart compatible Yixun Lan
2024-07-01 12:22 ` Conor Dooley
2024-06-27 15:31 ` [PATCH v2 07/10] riscv: add SpacemiT SOC family Kconfig support Yixun Lan
2024-07-01 12:25 ` Conor Dooley
2024-06-27 15:31 ` [PATCH v2 08/10] riscv: dts: add initial SpacemiT K1 SoC device tree Yixun Lan
2024-07-01 12:49 ` Emil Renner Berthing
2024-07-02 1:28 ` Yixun Lan
2024-07-02 1:35 ` Inochi Amaoto
2024-07-02 15:25 ` Conor Dooley
2024-07-03 9:40 ` Yixun Lan
2024-07-03 11:22 ` Emil Renner Berthing
2024-07-03 14:22 ` Yixun Lan
2024-06-27 15:31 ` [PATCH v2 09/10] riscv: dts: spacemit: add Banana Pi BPI-F3 board " Yixun Lan
2024-06-27 15:31 ` [PATCH v2 10/10] riscv: defconfig: enable SpacemiT SoC Yixun Lan
2024-07-01 12:21 ` Conor Dooley
2024-06-27 15:39 ` [PATCH v2 00/10] riscv: add initial support for SpacemiT K1 Conor Dooley
2024-06-27 15:56 ` Yixun Lan
2024-06-28 15:41 ` Rob Herring (Arm)
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=20240701-undercook-flatterer-7f18f7420a6d@spud \
--to=conor@kernel.org \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=cyy@cyyself.name \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=gregkh@linuxfoundation.org \
--cc=inochiama@outlook.com \
--cc=jirislaby@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=palmer@dabbelt.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tglx@linutronix.de \
--cc=zhangmeng.kevin@spacemit.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).