Devicetree
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Yangyu Chen <cyy@cyyself.name>
Cc: linux-riscv@lists.infradead.org,
	Damien Le Moal <dlemoal@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>, Guo Ren <guoren@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/7] dt-bindings: interrupt-controller: Add Canaan K230 PLIC
Date: Mon, 4 Mar 2024 20:33:14 +0000	[thread overview]
Message-ID: <20240304-froth-ecosphere-9ee29b2085ec@spud> (raw)
In-Reply-To: <tencent_23A08076AB6331AE43CC64C87FA3081F8006@qq.com>

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]

On Mon, Mar 04, 2024 at 11:16:23PM +0800, Yangyu Chen wrote:
> Add compatible string for Canaan K230 PLIC.
> 
> Signed-off-by: Yangyu Chen <cyy@cyyself.name>
> ---
>  .../bindings/interrupt-controller/sifive,plic-1.0.0.yaml         | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml b/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml
> index 709b2211276b..da147faf32bd 100644
> --- a/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml
> +++ b/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml
> @@ -69,6 +69,7 @@ properties:
>                - sophgo,cv1812h-plic
>                - sophgo,sg2042-plic
>                - thead,th1520-plic
> +              - canaan,k230-plic

Add this in alphanumerical order please.

>            - const: thead,c900-plic
>        - items:
>            - const: sifive,plic-1.0.0
> -- 
> 2.43.0
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-03-04 20:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 15:14 [PATCH v2 0/7] riscv: add initial support for Canaan Kendryte K230 Yangyu Chen
2024-03-04 15:16 ` [PATCH v2 1/7] dt-bindings: riscv: Add T-HEAD C908 compatible Yangyu Chen
2024-03-04 15:16 ` [PATCH v2 2/7] dt-bindings: add Canaan K230 boards compatible strings Yangyu Chen
2024-03-04 15:32   ` Krzysztof Kozlowski
2024-03-04 15:16 ` [PATCH v2 3/7] dt-bindings: timer: Add Canaan K230 CLINT Yangyu Chen
2024-03-04 20:33   ` Conor Dooley
2024-03-04 15:16 ` [PATCH v2 4/7] dt-bindings: interrupt-controller: Add Canaan K230 PLIC Yangyu Chen
2024-03-04 20:33   ` Conor Dooley [this message]
2024-03-04 15:16 ` [PATCH v2 5/7] riscv: Kconfig.socs: Allow SOC_CANAAN with MMU for K230 Yangyu Chen
2024-03-04 15:16 ` [PATCH v2 6/7] riscv: dts: add initial canmv-k230 and k230-evb dts Yangyu Chen
2024-03-04 20:35   ` Conor Dooley
2024-03-04 15:16 ` [PATCH v2 7/7] riscv: config: enable SOC_CANAAN in defconfig Yangyu Chen
2024-03-04 20:36   ` Conor Dooley

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=20240304-froth-ecosphere-9ee29b2085ec@spud \
    --to=conor@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=cyy@cyyself.name \
    --cc=devicetree@vger.kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=guoren@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@kernel.org \
    /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