linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: gregkh@linuxfoundation.org,
	linux-stm32@st-md-mailman.stormreply.com,
	Benjamin Gaignard <benjamin.gaignard@st.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm: kernel: initialize broadcast hrtimer based clock event device
Date: Tue, 12 Nov 2019 14:55:41 +0000	[thread overview]
Message-ID: <20191112145541.GK25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.21.1911121547490.1833@nanos.tec.linutronix.de>

On Tue, Nov 12, 2019 at 03:48:10PM +0100, Thomas Gleixner wrote:
> On Tue, 12 Nov 2019, Benjamin Gaignard wrote:
> 
> > On platforms implementing CPU power management, the CPUidle subsystem
> > can allow CPUs to enter idle states where local timers logic is lost on power
> > down. To keep the software timers functional the kernel relies on an
> > always-on broadcast timer to be present in the platform to relay the
> > interrupt signalling the timer expiries.
> > 
> > For platforms implementing CPU core gating that do not implement an always-on
> > HW timer or implement it in a broken way, this patch adds code to initialize
> > the kernel hrtimer based clock event device upon boot (which can be chosen as
> > tick broadcast device by the kernel).
> > It relies on a dynamically chosen CPU to be always powered-up. This CPU then
> > relays the timer interrupt to CPUs in deep-idle states through its HW local
> > timer device.
> > 
> > Having a CPU always-on has implications on power management platform
> > capabilities and makes CPUidle suboptimal, since at least a CPU is kept
> > always in a shallow idle state by the kernel to relay timer interrupts,
> > but at least leaves the kernel with a functional system with some working
> > power management capabilities.
> > 
> > The hrtimer based clock event device is unconditionally registered, but
> > has the lowest possible rating such that any broadcast-capable HW clock
> > event device present will be chosen in preference as the tick broadcast
> > device.
> > 
> > Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
> 
> Reviewed-by: Thomas Gleixner <tglx@linutronix.de>

Thanks.  Benjamin, please put it in the patch system, thanks.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-11-12 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12 12:06 [PATCH] arm: kernel: initialize broadcast hrtimer based clock event device Benjamin Gaignard
2019-11-12 14:48 ` Thomas Gleixner
2019-11-12 14:55   ` Russell King - ARM Linux admin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-10-15  8:41 Benjamin Gaignard
2019-10-29 12:43 ` Benjamin Gaignard

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=20191112145541.GK25745@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=benjamin.gaignard@st.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.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).