From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] clocksource: don't suspend/resume when unused
Date: Fri, 16 Jan 2015 18:45:16 +0100 [thread overview]
Message-ID: <20150116184516.735cd2de@bbrezillon> (raw)
In-Reply-To: <1421427439-11699-1-git-send-email-alexandre.belloni@free-electrons.com>
On Fri, 16 Jan 2015 17:57:17 +0100
Alexandre Belloni <alexandre.belloni@free-electrons.com> wrote:
> This is a quite naive implementation to track whether a clocksource is enabled.
> I chose not to add a member in struct clocksource and use a flag instead.
>
> I found that timekeeping.c is the only consumer for clocksource and I converted
> it to use clocksource_enable and clocksource_disable.
To the whole series:
Reviewed-by: Boris Brezillon <boris.brezillon@free-electrons.com>
>
> Changes in v2:
> - removed the check on enable in timekeeping.c to ensure all clocksources are
> going through clocksource_enable
> - rework clocksource_enable to set CLOCK_SOURCE_USED when enable is successful
> if present
>
> Alexandre Belloni (2):
> clocksource: track usage
> clocksource: don't suspend/resume when unused
>
> include/linux/clocksource.h | 4 ++++
> kernel/time/clocksource.c | 34 ++++++++++++++++++++++++++++++++--
> kernel/time/timekeeping.c | 8 +++-----
> 3 files changed, 39 insertions(+), 7 deletions(-)
>
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2015-01-16 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 16:57 [PATCH v2 0/2] clocksource: don't suspend/resume when unused Alexandre Belloni
2015-01-16 16:57 ` [PATCH v2 1/2] clocksource: track usage Alexandre Belloni
2015-01-16 19:05 ` John Stultz
2015-01-17 1:26 ` Alexandre Belloni
2015-01-20 10:51 ` Thomas Gleixner
2015-01-16 16:57 ` [PATCH v2 2/2] clocksource: don't suspend/resume when unused Alexandre Belloni
2015-01-20 11:13 ` Thomas Gleixner
2015-01-16 17:45 ` Boris Brezillon [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=20150116184516.735cd2de@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).