mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Markus Schneider-Pargmann" <msp@baylibre.com>
To: "Markus Schneider-Pargmann (TI)" <msp@baylibre.com>,
	"Daniel Lezcano" <daniel.lezcano@kernel.org>,
	"Thomas Gleixner" <tglx@kernel.org>
Cc: "H. Nikolaus Schaller" <hns@goldelico.com>,
	"Andreas Kemnade" <andreas@kemnade.info>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clocksource/drivers/timer-ti-dm: Register clocksource/event only for am654
Date: Wed, 16 Sep 2026 10:59:53 +0200	[thread overview]
Message-ID: <DLGM8U9HBK19.16WN58TZY1HXE@baylibre.com> (raw)
In-Reply-To: <20260828-v7-3-next-topic-ti-timer-dm-clocksource-omap-fix-v1-1-85f0e4dc6f9f@baylibre.com>

[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]

Hi Daniel,

On Fri Aug 28, 2026 at 8:47 PM CEST, Markus Schneider-Pargmann (TI) wrote:
> Registering clocksource/clockevent for the older platforms breaks
> booting them. The older platforms have their own implementation in early
> boot that is used to register clocksource/clockevent in
> timer-ti-dm-systimer.c.
>
> With am654, the timer is much more complex with more dependencies so
> doing this in early boot with the other driver is very difficult and
> gets ugly. Instead it is implemented in the platform driver for am654.
> However the old platforms may not register clocksource/clockevent in
> this driver as that would break the boot.
>
> Add a system_timer_capable flag that is only set for am654-timer that
> gates the clocksource/clockevent registration.
>
> Reported-by: H. Nikolaus Schaller <hns@goldelico.com>
> Closes: https://lore.kernel.org/r/2013A99A-0502-4128-ACFA-B04886224393@goldelico.com
> Fixes: b8eeeca55456 ("clocksource/drivers/timer-ti-dm: Add clocksource support")
> Signed-off-by: Markus Schneider-Pargmann (TI) <msp@baylibre.com>

Did you have time to take a look at this patch?

Thanks,
Markus

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 289 bytes --]

      parent reply	other threads:[~2026-09-16  9:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28 18:47 Markus Schneider-Pargmann (TI)
2026-08-28 21:04 ` Andreas Kemnade
2026-08-29  7:23   ` H. Nikolaus Schaller
2026-08-31 17:44     ` Kevin Hilman
2026-09-16  9:02     ` Markus Schneider-Pargmann
2026-09-16  8:59 ` Markus Schneider-Pargmann [this message]

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=DLGM8U9HBK19.16WN58TZY1HXE@baylibre.com \
    --to=msp@baylibre.com \
    --cc=andreas@kemnade.info \
    --cc=daniel.lezcano@kernel.org \
    --cc=hns@goldelico.com \
    --cc=linux-kernel@vger.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®