linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	Will Deacon <will@kernel.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: [PATCH 0/2] Use Exynos-MCT timer as wakeup for Arm arch timer
Date: Tue,  8 Jun 2021 16:43:39 +0100	[thread overview]
Message-ID: <20210608154341.10794-1-will@kernel.org> (raw)

Hi all,

These two patches build on top of my other series for adding per-cpu
wakeup timers [1] which is currently queued in -tip [2].

The basic idea is to prefer the Arm architected timer, even when
CLOCK_EVT_FEAT_C3STOP is set, as long as we have another timer which can
be used for the per-cpu wakeup. These patches use Exynos-MCT as an
example, since that driver currently goes out of its way to prevent use
of the Arm architected timer due to issues with a 32-bit SoC.

Cheers,

Will

[1] https://lore.kernel.org/lkml/20210524221818.15850-1-will@kernel.org/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=timers/core

Cc: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: Chanwoo Choi <cw00.choi@samsung.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>

--->8

Will Deacon (2):
  clocksource/drivers/exynos_mct: Prioritise Arm arch timer on arm64
  clocksource/drivers/exynos_mct: Mark MCT device as
    CLOCK_EVT_FEAT_PERCPU

 drivers/clocksource/exynos_mct.c | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

-- 
2.32.0.rc1.229.g3e70b5a671-goog


             reply	other threads:[~2021-06-08 15:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 15:43 Will Deacon [this message]
2021-06-08 15:43 ` [PATCH 1/2] clocksource/drivers/exynos_mct: Prioritise Arm arch timer on arm64 Will Deacon
2021-06-09 11:41   ` Krzysztof Kozlowski
2021-06-10  1:03   ` Chanwoo Choi
2021-06-16 15:25     ` Daniel Lezcano
2021-06-17  0:58       ` Chanwoo Choi
2021-06-17 21:47         ` Will Deacon
2021-06-21  9:25           ` Daniel Lezcano
2021-06-21 10:10             ` Will Deacon
2021-06-21 10:18               ` Daniel Lezcano
2021-06-22  2:40                 ` Chanwoo Choi
2021-06-22  5:21                   ` Daniel Lezcano
2021-06-22  6:42                     ` Chanwoo Choi
2021-06-21 10:17             ` Marek Szyprowski
2021-06-21 10:24               ` Daniel Lezcano
2021-08-26 16:25   ` [tip: timers/core] " tip-bot2 for Will Deacon
2021-06-08 15:43 ` [PATCH 2/2] clocksource/drivers/exynos_mct: Mark MCT device as CLOCK_EVT_FEAT_PERCPU Will Deacon
2021-06-09 11:41   ` Krzysztof Kozlowski
2021-06-17  0:59   ` Chanwoo Choi
2021-08-26 16:25   ` [tip: timers/core] " tip-bot2 for Will Deacon

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=20210608154341.10794-1-will@kernel.org \
    --to=will@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=krzk@kernel.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.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).