From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Alim Akhtar <alim.akhtar@samsung.com>,
Ingo Molnar <mingo@kernel.org>,
Peter Griffin <peter.griffin@linaro.org>,
Youngmin Nam <youngmin.nam@samsung.com>
Subject: Re: [PATCH] clocksource/drivers/exynos_mct: Use percpu interrupts only on ARM64
Date: Fri, 19 Sep 2025 23:31:25 +0200 [thread overview]
Message-ID: <d27df41d-58ba-41e8-9275-2e9991f574a0@samsung.com> (raw)
In-Reply-To: <8fb4534e-ffb0-40ad-8256-b0fa040a1b97@kernel.org>
On 27.08.2025 13:58, Krzysztof Kozlowski wrote:
> On 27/08/2025 12:26, Marek Szyprowski wrote:
>> For some unknown reasons forcing percpu interrupts for local timers
>> breaks CPU hotplug for 'little' cores on legacy ARM 32bit Exynos based
>> machines (for example Exynos5422-based Odroid-XU3/XU4 boards). Use percpu
>> flag only when driver is compiled for newer ARM64 architecture.
>>
>> Fixes: f3cec54ee3bf ("clocksource/drivers/exynos_mct: Set local timer interrupts as percpu")
>
> I am pretty sure the patch above was not tested on arm32, thus this
> workaround seems reasonable.
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Daniel, any chance to get this merged?
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
next prev parent reply other threads:[~2025-09-19 21:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250827102650eucas1p1fe270adbf29c649b9ce529e1d45aabc3@eucas1p1.samsung.com>
2025-08-27 10:26 ` [PATCH] clocksource/drivers/exynos_mct: Use percpu interrupts only on ARM64 Marek Szyprowski
2025-08-27 11:58 ` Krzysztof Kozlowski
2025-09-19 21:31 ` Marek Szyprowski [this message]
2025-09-24 8:41 ` Daniel Lezcano
2025-09-24 8:53 ` Marek Szyprowski
2025-09-24 17:17 ` William McVicker
2025-09-25 6:37 ` Marek Szyprowski
2025-09-25 8:07 ` Daniel Lezcano
2025-09-23 10:09 ` Peter Griffin
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=d27df41d-58ba-41e8-9275-2e9991f574a0@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=daniel.lezcano@linaro.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peter.griffin@linaro.org \
--cc=tglx@linutronix.de \
--cc=youngmin.nam@samsung.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;
as well as URLs for NNTP newsgroup(s).