From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-kernel@vger.kernel.org, mark.rutland@arm.com,
linux-sh@vger.kernel.org, marc.zyngier@arm.com,
catalin.marinas@arm.com, horms@verge.net.au,
john.stultz@linaro.org, shinya.kuribayashi.px@renesas.com,
tglx@linutronix.de
Subject: Re: [PATCH/RFC] clockevents: Ignore C3STOP when CPUIdle is disabled
Date: Tue, 18 Jun 2013 10:30:15 +0200 [thread overview]
Message-ID: <51C01A97.5000903@linaro.org> (raw)
In-Reply-To: <20130618071756.22598.51046.sendpatchset@w520>
On 06/18/2013 09:17 AM, Magnus Damm wrote:
> From: Magnus Damm <damm@opensource.se>
>
> Introduce the function tick_device_may_c3stop() that
> ignores the C3STOP flag in case CPUIdle is disabled.
>
> The C3STOP flag tells the system that a clock event
> device may be stopped during deep sleep, but if this
> will happen or not depends on things like if CPUIdle
> is enabled and if a CPUIdle driver is available.
>
> This patch assumes that if CPUIdle is disabled then
> the sleep mode triggering C3STOP will never be entered.
> So by ignoring C3STOP when CPUIdle is disabled then it
> becomes possible to use high resolution timers with only
> per-cpu local timers - regardless if they have the
> C3STOP flag set or not.
>
> Observed on the r8a73a4 SoC that at this point only uses
> ARM architected timers for clock event and clock sources.
>
> Without this patch high resolution timers are run time
> disabled on the r8a73a4 SoC - this regardless of CPUIdle
> is disabled or not.
>
> The less short term fix is to add support for more timers
> on the r8a73a4 SoC, but until CPUIdle support is enabled
> it must be possible to use high resoultion timers without
> additional timers.
>
> I'd like to hear some feedback and also test this on more
> systems before merging the code, see the non-SOB below.
>
> Not-Yet-Signed-off-by: Magnus Damm <damm@opensource.se>
> ---
>
> An earlier ARM arch timer specific version of this patch was
> posted yesterday as:
> "[PATCH/RFC] arm: arch_timer: Do not set C3STOP in case CPU_IDLE=n"
>
> Many thanks to Mark Rutland for his kind feedback.
>
> kernel/time/tick-broadcast.c | 8 ++++----
> kernel/time/tick-common.c | 2 +-
> kernel/time/tick-internal.h | 11 +++++++++++
> 3 files changed, 16 insertions(+), 5 deletions(-)
>
> --- 0001/kernel/time/tick-broadcast.c
> +++ work/kernel/time/tick-broadcast.c 2013-06-18 15:36:21.000000000 +0900
> @@ -71,7 +71,7 @@ int tick_check_broadcast_device(struct c
> if ((dev->features & CLOCK_EVT_FEAT_DUMMY) ||
> (tick_broadcast_device.evtdev &&
> tick_broadcast_device.evtdev->rating >= dev->rating) ||
> - (dev->features & CLOCK_EVT_FEAT_C3STOP))
> + tick_device_may_c3stop(dev))
> return 0;
>
> clockevents_exchange_device(tick_broadcast_device.evtdev, dev);
> @@ -146,7 +146,7 @@ int tick_device_uses_broadcast(struct cl
> * feature and the cpu is marked in the broadcast mask
> * then clear the broadcast bit.
> */
> - if (!(dev->features & CLOCK_EVT_FEAT_C3STOP)) {
> + if (!tick_device_may_c3stop(dev)) {
> int cpu = smp_processor_id();
> cpumask_clear_cpu(cpu, tick_broadcast_mask);
> tick_broadcast_clear_oneshot(cpu);
> @@ -270,7 +270,7 @@ static void tick_do_broadcast_on_off(uns
> /*
> * Is the device not affected by the powerstate ?
> */
> - if (!dev || !(dev->features & CLOCK_EVT_FEAT_C3STOP))
> + if (!dev || !tick_device_may_c3stop(dev))
> goto out;
>
> if (!tick_device_is_functional(dev))
> @@ -568,7 +568,7 @@ void tick_broadcast_oneshot_control(unsi
> td = &per_cpu(tick_cpu_device, cpu);
> dev = td->evtdev;
>
> - if (!(dev->features & CLOCK_EVT_FEAT_C3STOP))
> + if (!tick_device_may_c3stop(dev))
> return;
>
> bc = tick_broadcast_device.evtdev;
> --- 0001/kernel/time/tick-common.c
> +++ work/kernel/time/tick-common.c 2013-06-18 15:36:29.000000000 +0900
> @@ -52,7 +52,7 @@ int tick_is_oneshot_available(void)
>
> if (!dev || !(dev->features & CLOCK_EVT_FEAT_ONESHOT))
> return 0;
> - if (!(dev->features & CLOCK_EVT_FEAT_C3STOP))
> + if (!tick_device_may_c3stop(dev))
> return 1;
> return tick_broadcast_oneshot_available();
> }
> --- 0001/kernel/time/tick-internal.h
> +++ work/kernel/time/tick-internal.h 2013-06-18 15:40:10.000000000 +0900
> @@ -141,6 +141,17 @@ static inline int tick_device_is_functio
> return !(dev->features & CLOCK_EVT_FEAT_DUMMY);
> }
>
> +/*
> + * Check, if the device has C3STOP behavior and CPU Idle is enabled
> + */
> +static inline bool tick_device_may_c3stop(struct clock_event_device *dev)
I prefer tick_device_is_reliable(struct clock_event_device *dev).
> +{
> + /* The C3 sleep mode can only trigger when CPU Idle is enabled,
> + * so if CPU Idle is disabled then the C3STOP flag can be ignored */
> + return (IS_ENABLED(CONFIG_CPU_IDLE) &&
> + (dev->features & CLOCK_EVT_FEAT_C3STOP));
> +}
Preferably you may use the format:
#ifdef CONFIG_CPU_IDLE
static inline bool tick_device_is_reliable(struct clock_event_device *dev)
{
return dev->features & CLOCK_EVT_FEAT_C3STOP;
}
#else
static inline bool tick_device_is_reliable(struct clock_event_device *dev)
{
return true;
}
#endif
to conform the header style format already present in the file.
> extern void do_timer(unsigned long ticks);
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2013-06-18 8:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 7:17 [PATCH/RFC] clockevents: Ignore C3STOP when CPUIdle is disabled Magnus Damm
2013-06-18 7:32 ` Daniel Lezcano
2013-06-18 7:39 ` Magnus Damm
2013-06-18 8:24 ` Daniel Lezcano
2013-06-18 8:49 ` Magnus Damm
2013-06-19 13:55 ` Daniel Lezcano
2013-06-18 8:30 ` Daniel Lezcano [this message]
2013-06-18 8:56 ` Magnus Damm
2013-06-19 13:53 ` Daniel Lezcano
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=51C01A97.5000903@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=horms@verge.net.au \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=shinya.kuribayashi.px@renesas.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