From: Marc Zyngier <maz@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Steven Price <steven.price@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Hanjun Guo <guohanjun@huawei.com>,
Sudeep Holla <sudeep.holla@arm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH 2/4] clocksource/drivers/arm_arch_timer: Add standalone MMIO driver
Date: Thu, 14 Aug 2025 11:49:26 +0100 [thread overview]
Message-ID: <86ldnmdvpl.wl-maz@kernel.org> (raw)
In-Reply-To: <8e58b01b-772d-4ca7-a681-34f10baa07e6@arm.com>
On Thu, 14 Aug 2025 11:13:47 +0100,
Steven Price <steven.price@arm.com> wrote:
>
> On 07/08/2025 17:02, Marc Zyngier wrote:
> > Add a new driver for the MMIO side of the ARM architected timer.
> > Most of it has been lifted from the existing arch timer code,
> > massaged, and finally rewritten.
> >
> > It supports both DT and ACPI as firmware descriptions.
> >
> > Signed-off-by: Marc Zyngier <maz@kernel.org>
> > ---
> > MAINTAINERS | 1 +
> > drivers/clocksource/arm_arch_timer_mmio.c | 420 ++++++++++++++++++++++
> > 2 files changed, 421 insertions(+)
> > create mode 100644 drivers/clocksource/arm_arch_timer_mmio.c
> >
> [...]
> > +static void arch_timer_mmio_setup(struct arch_timer *at, int irq)
> > +{
> > + at->evt = (struct clock_event_device) {
> > + .features = (CLOCK_EVT_FEAT_ONESHOT |
> > + CLOCK_EVT_FEAT_DYNIRQ),
> > + .name = "arch_mem_timer",
> > + .rating = 400,
> > + .cpumask = cpu_possible_mask,
> > + .irq = irq,
> > + .set_next_event = arch_timer_mmio_set_next_event,
> > + .set_state_oneshot_stopped = arch_timer_mmio_shutdown,
> > + .set_state_shutdown = arch_timer_mmio_shutdown,
> > + };
> > +
> > + at->evt.set_state_shutdown(&at->evt);
> > +
> > + clockevents_config_and_register(&at->evt, at->rate, 0xf, CLOCKSOURCE_MASK(56));
>
> This doesn't work on 32 bit - clockevents_config_and_register()'s final
> argument is an unsigned long, and a 56 bit mask doesn't fit. This
> triggers a compiler warning:
Already reported, see 20250814111657.7debc9f1@canb.auug.org.au.
> Possible this should really be min(CLOCKSOURCE_MASK(56), ULONG_MAX)? But
> I'm not familiar enough with this code. Most likely it's dead code on a
> 32 bit platform.
No, this definitely exists on 32bit crap, since it has been part of
the architecture from the ARMv7+VE days.
I think this is more of an impedance mismatch between the
CLOCKSOURCE_MASK() helper and the clockevents_config_and_register(),
and a (unsigned long) cast would do the trick.
But it also means that the per-cpu timer also gets truncated the same
way, and that has interesting impacts on how often the timer is
reprogrammed.
Daniel, do you want a patch on top or a new series?
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-08-14 10:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 16:02 [PATCH 0/4] clocksource: Add standalone MMIO ARM arch timer driver Marc Zyngier
2025-08-07 16:02 ` [PATCH 1/4] ACPI: GTDT: Generate platform devices for MMIO timers Marc Zyngier
2025-08-07 16:02 ` [PATCH 2/4] clocksource/drivers/arm_arch_timer: Add standalone MMIO driver Marc Zyngier
2025-08-14 10:13 ` Steven Price
2025-08-14 10:49 ` Marc Zyngier [this message]
2025-08-14 11:14 ` Marc Zyngier
2025-08-14 12:23 ` Steven Price
2025-08-14 12:42 ` Marc Zyngier
2025-08-14 14:02 ` Daniel Lezcano
2025-08-07 16:02 ` [PATCH 3/4] clocksource/drivers/arm_arch_timer_mmio: Switch over to standalone driver Marc Zyngier
2025-08-07 16:02 ` [PATCH 4/4] clocksource/drivers/arm_arch_timer_mmio: Add MMIO clocksource Marc Zyngier
2025-08-13 10:55 ` [PATCH 0/4] clocksource: Add standalone MMIO ARM arch timer driver Sudeep Holla
2025-08-13 11:35 ` Alexandru Elisei
2025-08-13 11:49 ` Marc Zyngier
2025-08-13 12:03 ` Daniel Lezcano
2025-08-13 12:32 ` Sudeep Holla
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=86ldnmdvpl.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=guohanjun@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=rafael@kernel.org \
--cc=steven.price@arm.com \
--cc=sudeep.holla@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).