From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: geert@linux-m68k.org, tglx@kernel.org, miodrag.dinic@mips.com
Cc: radu@rendec.net, zewenchen@google.com, jamiechen@google.com,
edwardwchen@google.com, marscheng@google.com,
eleanor15x@gmail.com, jserv@ccns.ncku.edu.tw,
linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
Kuan-Wei Chiu <visitorckw@gmail.com>
Subject: [PATCH 0/6] m68k: virt: Switch to generic goldfish PIC driver
Date: Tue, 8 Sep 2026 09:40:10 +0000 [thread overview]
Message-ID: <20260908094016.1997918-1-visitorckw@gmail.com> (raw)
Convert the m68k virt machine to use the generic goldfish PIC irqchip
driver instead of maintaining a duplicate, platform-specific interrupt
controller implementation in arch/m68k/virt/.
The whole patchset is tested on qemu-system-m68k -M virt and verified
that interrupts across multiple goldfish PIC instances fire and
increment properly in /proc/interrupts.
---
P.S. From a quick search on lore, Miodrag has been inactive on LKML for
a while. His last appearance was just handing over the goldfish-rtc
driver 6 years ago, and prior to that it goes all the way back to 2017.
With tglx's recent call for irqchip reviews in mind, I actually use and
care about goldfish devices on qemu for both linux and u-boot, so I'm
happy to help review future patches for this driver. I can follow up
with a MAINTAINERS patch if that sounds good.
Kuan-Wei Chiu (6):
irqchip/goldfish-pic: Use gf_ioread32/gf_iowrite32 for MMIO access
irqchip/goldfish-pic: Use for_each_set_bit() to iterate pending IRQ
irqchip/goldfish-pic: Allow selecting CONFIG_GOLDFISH_PIC on other
architectures
irqchip/goldfish-pic: Add goldfish_pic_init() for non DT platforms
m68k/irq: Add empty irq_eoi callback to auto/user IRQ chips
m68k: virt: Switch to generic goldfish-pic driver
MAINTAINERS | 1 +
arch/m68k/Kconfig.machine | 1 +
arch/m68k/kernel/ints.c | 6 ++
arch/m68k/virt/ints.c | 89 ++----------------
drivers/irqchip/Kconfig | 2 +-
drivers/irqchip/irq-goldfish-pic.c | 113 +++++++++++++++--------
include/linux/irqchip/irq-goldfish-pic.h | 15 +++
7 files changed, 105 insertions(+), 122 deletions(-)
create mode 100644 include/linux/irqchip/irq-goldfish-pic.h
--
2.55.0.979.g7e5102b832-goog
next reply other threads:[~2026-09-08 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 9:40 Kuan-Wei Chiu [this message]
2026-09-08 9:40 ` [PATCH 1/6] irqchip/goldfish-pic: Use gf_ioread32/gf_iowrite32 for MMIO access Kuan-Wei Chiu
2026-09-08 9:40 ` [PATCH 2/6] irqchip/goldfish-pic: Use for_each_set_bit() to iterate pending IRQ Kuan-Wei Chiu
2026-09-08 9:40 ` [PATCH 3/6] irqchip/goldfish-pic: Allow selecting CONFIG_GOLDFISH_PIC on other architectures Kuan-Wei Chiu
2026-09-08 9:40 ` [PATCH 4/6] irqchip/goldfish-pic: Add goldfish_pic_init() for non DT platforms Kuan-Wei Chiu
2026-09-08 9:40 ` [PATCH 5/6] m68k/irq: Add empty irq_eoi callback to auto/user IRQ chips Kuan-Wei Chiu
2026-09-08 9:40 ` [PATCH 6/6] m68k: virt: Switch to generic goldfish-pic driver Kuan-Wei Chiu
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=20260908094016.1997918-1-visitorckw@gmail.com \
--to=visitorckw@gmail.com \
--cc=edwardwchen@google.com \
--cc=eleanor15x@gmail.com \
--cc=geert@linux-m68k.org \
--cc=jamiechen@google.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=marscheng@google.com \
--cc=miodrag.dinic@mips.com \
--cc=radu@rendec.net \
--cc=tglx@kernel.org \
--cc=zewenchen@google.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
all inboxes | Powered by JetHome®