From: guoren@kernel.org
To: guoren@kernel.org, anup@brainfault.org, atish.patra@wdc.com,
maz@kernel.org, tglx@linutronix.de, palmer@dabbelt.com,
heiko@sntech.de
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
Guo Ren <guoren@linux.alibaba.com>, Rob Herring <robh@kernel.org>,
Palmer Dabbelt <palmerdabbelt@google.com>
Subject: [PATCH V3 1/2] dt-bindings: update riscv plic compatible string
Date: Wed, 13 Oct 2021 09:21:48 +0800 [thread overview]
Message-ID: <20211013012149.2834212-1-guoren@kernel.org> (raw)
From: Guo Ren <guoren@linux.alibaba.com>
Add the compatible string "thead,c900-plic" to the riscv plic
bindings to support SOCs with thead,c9xx processor cores.
Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
Cc: Rob Herring <robh@kernel.org>
Cc: Palmer Dabbelt <palmerdabbelt@google.com>
Cc: Anup Patel <anup@brainfault.org>
Cc: Atish Patra <atish.patra@wdc.com>
---
Changes since V3:
- Rename "c9xx" to "c900"
- Add thead,c900-plic in the description section
---
.../bindings/interrupt-controller/sifive,plic-1.0.0.yaml | 6 ++++++
1 file changed, 6 insertions(+)
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 08d5a57ce00f..82629832e5a5 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
@@ -35,6 +35,11 @@ description:
contains a specific memory layout, which is documented in chapter 8 of the
SiFive U5 Coreplex Series Manual <https://static.dev.sifive.com/U54-MC-RVCoreIP.pdf>.
+ While the "thead,c900-plic" would mask IRQ with readl(claim), so it needn't
+ mask/unmask which needed in RISC-V PLIC. When in IRQS_ONESHOT & IRQCHIP_EOI_THREADED
+ path, unnecessary mask operation would cause a blocking irq bug in thead,c900-plic.
+ Because when IRQ is disabled in c900, writel(hwirq, claim) would be invalid.
+
maintainers:
- Sagar Kadam <sagar.kadam@sifive.com>
- Paul Walmsley <paul.walmsley@sifive.com>
@@ -46,6 +51,7 @@ properties:
- enum:
- sifive,fu540-c000-plic
- canaan,k210-plic
+ - thead,c900-plic
- const: sifive,plic-1.0.0
reg:
--
2.25.1
next reply other threads:[~2021-10-13 1:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 1:21 guoren [this message]
2021-10-13 1:21 ` [PATCH V3 2/2] irqchip/sifive-plic: Add thead,c900-plic support guoren
2021-10-13 5:04 ` Anup Patel
2021-10-13 8:38 ` Guo Ren
2021-10-13 5:11 ` [PATCH V3 1/2] dt-bindings: update riscv plic compatible string Anup Patel
2021-10-13 8:57 ` Heiko Stübner
2021-10-13 9:11 ` Anup Patel
2021-10-13 9:14 ` Heiko Stübner
2021-10-13 9:19 ` Anup Patel
2021-10-13 9:43 ` Heiko Stübner
2021-10-13 9:49 ` Anup Patel
2021-10-13 10:58 ` Heiko Stübner
2021-10-13 12:49 ` Guo Ren
2021-10-14 0:25 ` Heiko Stuebner
2021-10-14 1:56 ` Guo Ren
2021-10-14 4:21 ` Samuel Holland
2021-10-14 6:17 ` Guo Ren
2021-10-13 12:34 ` Guo Ren
2021-10-13 12:39 ` Marc Zyngier
2021-10-13 12:42 ` Guo Ren
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=20211013012149.2834212-1-guoren@kernel.org \
--to=guoren@kernel.org \
--cc=anup@brainfault.org \
--cc=atish.patra@wdc.com \
--cc=guoren@linux.alibaba.com \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=palmer@dabbelt.com \
--cc=palmerdabbelt@google.com \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
/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