From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: daniel.lezcano@kernel.org, tglx@kernel.org
Cc: pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, geert@linux-m68k.org, laurent@vivier.eu,
marscheng@google.com, eleanor15x@gmail.com,
jserv@ccns.ncku.edu.tw, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-m68k@lists.linux-m68k.org,
Kuan-Wei Chiu <visitorckw@gmail.com>
Subject: [PATCH 0/8] clocksource/drivers/timer-goldfish: Fix bugs and add DT support
Date: Thu, 5 Nov 2026 16:16:54 +0000 [thread overview]
Message-ID: <20261105161702.3515900-1-visitorckw@gmail.com> (raw)
The goldfish timer driver was previously only used and tested on
single core m68k virt, but the same device is also present on other
qemu virt machines such as riscv and or1k, where running on SMP exposes
several issues.
Fix the concurrency, oneshot, and registration bugs in the driver, add
device tree probing support so it can be used across these platforms,
and add a MAINTAINERS entry.
Tested on qemu m68k virt and on qemu riscv64 virt with 4 SMP cores. On
riscv64, testing was done by passing clocksource=goldfish_timer on the
kernel command line and locally bumping the clock_event_device rating
above the architected timer to verify both clocksource and oneshot
clockevent operation.
Kuan-Wei Chiu (8):
clocksource/drivers/timer-goldfish: Fix latch corruption with spinlock
clocksource/drivers/timer-goldfish: Fix oneshot mode spurious
interrupt
clocksource/drivers/timer-goldfish: Fix resource leaks in init
clocksource/drivers/timer-goldfish: Set CLOCK_SOURCE_IS_CONTINUOUS
flag
clocksource/drivers/timer-goldfish: Drop redundant max_idle_ns setting
clocksource/drivers/timer-goldfish: Set clock_event_device cpumask
clocksource/drivers/timer-goldfish: Add device tree probing support
MAINTAINERS: Add entry for goldfish timer driver
MAINTAINERS | 6 ++
drivers/clocksource/Kconfig | 5 +-
drivers/clocksource/timer-goldfish.c | 113 +++++++++++++++++++++------
3 files changed, 99 insertions(+), 25 deletions(-)
--
2.56.0.398.g882cbad275-goog
next reply other threads:[~2026-11-05 16:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 16:16 Kuan-Wei Chiu [this message]
2026-11-05 16:16 ` [PATCH 1/8] clocksource/drivers/timer-goldfish: Fix latch corruption with spinlock Kuan-Wei Chiu
2026-11-05 16:16 ` [PATCH 2/8] clocksource/drivers/timer-goldfish: Fix oneshot mode spurious interrupt Kuan-Wei Chiu
2026-11-05 16:16 ` [PATCH 3/8] clocksource/drivers/timer-goldfish: Fix resource leaks in init Kuan-Wei Chiu
2026-11-05 16:16 ` [PATCH 4/8] clocksource/drivers/timer-goldfish: Set CLOCK_SOURCE_IS_CONTINUOUS flag Kuan-Wei Chiu
2026-11-05 16:16 ` [PATCH 5/8] clocksource/drivers/timer-goldfish: Drop redundant max_idle_ns setting Kuan-Wei Chiu
2026-11-05 16:17 ` [PATCH 6/8] clocksource/drivers/timer-goldfish: Set clock_event_device cpumask Kuan-Wei Chiu
2026-11-05 16:17 ` [PATCH 7/8] clocksource/drivers/timer-goldfish: Add device tree probing support Kuan-Wei Chiu
2026-11-05 16:17 ` [PATCH 8/8] MAINTAINERS: Add entry for goldfish timer 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=20261105161702.3515900-1-visitorckw@gmail.com \
--to=visitorckw@gmail.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=daniel.lezcano@kernel.org \
--cc=eleanor15x@gmail.com \
--cc=geert@linux-m68k.org \
--cc=jserv@ccns.ncku.edu.tw \
--cc=laurent@vivier.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-riscv@lists.infradead.org \
--cc=marscheng@google.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=tglx@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
all inboxes | Powered by JetHome®