From: Kevin Hilman <khilman@kernel.org>
To: "H. Nikolaus Schaller" <hns@goldelico.com>,
"Markus Schneider-Pargmann (TI)" <msp@baylibre.com>
Cc: Andreas Kemnade <andreas@kemnade.info>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Thomas Gleixner <tglx@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
letux-kernel@openphoenux.org
Subject: Re: [PATCH] clocksource/drivers/timer-ti-dm: Register clocksource/event only for am654
Date: Mon, 31 Aug 2026 10:44:48 -0700 [thread overview]
Message-ID: <7hzey26v73.fsf@baylibre.com> (raw)
In-Reply-To: <E27F05E3-DE4F-4C77-95E3-1701B3410E93@goldelico.com>
"H. Nikolaus Schaller" <hns@goldelico.com> writes:
>> Am 28.08.2026 um 23:04 schrieb Andreas Kemnade <andreas@kemnade.info>:
>>
>> On Fri, 28 Aug 2026 20:47:45 +0200
>> "Markus Schneider-Pargmann (TI)" <msp@baylibre.com> 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>
>>
>> Tested-by: Andreas Kemnade <andreas@kemnade.info> # OMAP3 GTA04
>
> Tested-by: H. Nikolaus Schaller <hns@goldelico.com> # OMAP3 OpenPandora
>
Tested-by: Kevin Hilman <khilman@baylibre.com> # OMAP3 Beagle XM
next prev parent reply other threads:[~2026-08-31 17:44 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 [this message]
2026-09-16 9:02 ` Markus Schneider-Pargmann
2026-09-16 8:59 ` Markus Schneider-Pargmann
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=7hzey26v73.fsf@baylibre.com \
--to=khilman@kernel.org \
--cc=andreas@kemnade.info \
--cc=daniel.lezcano@kernel.org \
--cc=hns@goldelico.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=msp@baylibre.com \
--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®