From: anup@brainfault.org (Anup Patel)
To: linux-riscv@lists.infradead.org
Subject: [RFC PATCH 0/5] New RISC-V Local Interrupt Controller Driver
Date: Tue, 4 Sep 2018 18:15:09 +0530 [thread overview]
Message-ID: <20180904124514.6290-1-anup@brainfault.org> (raw)
This patchset provides a new RISC-V Local Interrupt Controller Driver
for managing per-CPU local interrupts. The overall approach is inspired
from the way per-CPU local interrupts are handled by Linux ARM64 and
ARM GICv3 driver.
Few advantages of having this new driver are as follows:
1. It registers all local interrupts as per-CPU interrupts
2. We can develop drivers for devices with per-CPU local interrupts
without changing arch code or this driver
3. It allows local interrupt controller DT node under each CPU DT node
as well as single system-wide DT node for local interrupt controller.
With this patchset, output of "cat /proc/interrupts" looks as follows:
CPU0 CPU1 CPU2 CPU3
5: 995 1012 997 1015 RISC-V INTC 5 Edge riscv_timer
8: 23 6 10 7 SiFive PLIC 8 Edge virtio0
10: 9 10 5 4 SiFive PLIC 10 Edge ttyS0
The patchset is based up Linux-4.19-rc2 and can be found at
riscv_intc_v1 branch of:
https://github.com/avpatel/linux.git
Anup Patel (5):
RISC-V: Make IPI triggering flexible
RISC-V: No need to pass scause as arg to do_IRQ()
RISC-V: Select useful GENERIC_IRQ kconfig options
irqchip: RISC-V Local Interrupt Controller Driver
clocksource: riscv_timer: Make timer interrupt as a per-CPU interrupt
arch/riscv/Kconfig | 4 +
arch/riscv/include/asm/irq.h | 16 ++-
arch/riscv/include/asm/smp.h | 10 ++
arch/riscv/kernel/entry.S | 1 -
arch/riscv/kernel/irq.c | 45 +--------
arch/riscv/kernel/smp.c | 23 ++++-
drivers/clocksource/riscv_timer.c | 76 ++++++++++++---
drivers/irqchip/Kconfig | 15 ++-
drivers/irqchip/Makefile | 1 +
drivers/irqchip/irq-riscv-intc.c | 156 ++++++++++++++++++++++++++++++
drivers/irqchip/irq-sifive-plic.c | 21 +++-
include/linux/cpuhotplug.h | 1 +
12 files changed, 301 insertions(+), 68 deletions(-)
create mode 100644 drivers/irqchip/irq-riscv-intc.c
--
2.17.1
next reply other threads:[~2018-09-04 12:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 12:45 Anup Patel [this message]
2018-09-04 12:45 ` [RFC PATCH 1/5] RISC-V: Make IPI triggering flexible Anup Patel
2018-09-04 18:50 ` Christoph Hellwig
2018-09-05 4:36 ` Anup Patel
2018-09-05 18:56 ` Christoph Hellwig
2018-09-06 9:45 ` Palmer Dabbelt
2018-09-06 10:45 ` Anup Patel
2018-09-10 13:34 ` Christoph Hellwig
2018-09-11 3:37 ` Anup Patel
2018-09-29 1:45 ` Palmer Dabbelt
2018-09-29 1:45 ` Palmer Dabbelt
2018-09-29 7:06 ` Anup Patel
2018-09-29 7:06 ` Anup Patel
2018-09-04 12:45 ` [RFC PATCH 2/5] RISC-V: No need to pass scause as arg to do_IRQ() Anup Patel
2018-09-04 18:50 ` Christoph Hellwig
2018-09-04 12:45 ` [RFC PATCH 3/5] RISC-V: Select useful GENERIC_IRQ kconfig options Anup Patel
2018-09-04 18:56 ` Christoph Hellwig
2018-09-05 4:52 ` Anup Patel
2018-09-05 18:57 ` Christoph Hellwig
2018-09-04 12:45 ` [RFC PATCH 4/5] irqchip: RISC-V Local Interrupt Controller Driver Anup Patel
2018-09-04 18:57 ` Christoph Hellwig
2018-09-05 6:09 ` Anup Patel
2018-09-05 18:58 ` Christoph Hellwig
2018-09-06 11:53 ` Anup Patel
2018-09-10 13:35 ` Christoph Hellwig
2018-09-04 12:45 ` [RFC PATCH 5/5] clocksource: riscv_timer: Make timer interrupt as a per-CPU interrupt Anup Patel
2018-09-04 18:58 ` Christoph Hellwig
2018-09-05 8:21 ` Anup Patel
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=20180904124514.6290-1-anup@brainfault.org \
--to=anup@brainfault.org \
--cc=linux-riscv@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).