From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Kconfig: select GENERIC_CLOCKEVENTS_BROADCAST also on UP
Date: Mon, 30 Jan 2017 13:53:48 +0000 [thread overview]
Message-ID: <20170130135348.GS27312@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20170120163230.9357-1-l.stach@pengutronix.de>
On Fri, Jan 20, 2017 at 05:32:30PM +0100, Lucas Stach wrote:
> Quite a few systems have deeper idle states where the local timer tick
> stops to fire, that rely on the GENERIC_CLOCKEVENTS_BROADCAST
> infrastructure to switch to a global (non-stopping) clockevent device.
> This is also true on UP systems, so select GENERIC_CLOCKEVENTS_BROADCAST
> unconditionally.
>
> Instead only select ARCH_HAS_TICK_BROADCAST if SMP is present, as this
> is only implemented for SMP systems.
>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> ---
> v2: Only select GENERIC_CLOCKEVENTS_BROADCAST if the architecture
> supports GENERIC_CLOCKEVENTS.
Provided this solves the problems identified by the 0-day builder with
your previous patch, please submit it to the patch system, thanks.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2017-01-30 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 16:32 [PATCH] ARM: Kconfig: select GENERIC_CLOCKEVENTS_BROADCAST also on UP Lucas Stach
2017-01-30 13:53 ` Russell King - ARM Linux [this message]
2017-02-07 10:57 ` Russell King - ARM Linux
-- strict thread matches above, loose matches on Subject: below --
2016-07-08 15:58 Lucas Stach
2016-09-16 9:32 ` Lucas Stach
2016-09-16 10:20 ` Russell King - ARM Linux
2016-09-16 10:30 ` Thomas Gleixner
2016-09-16 11:08 ` Lucas Stach
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=20170130135348.GS27312@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--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).