From: marc_gonzalez@sigmadesigns.com (Marc Gonzalez)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] twd: Don't set CLOCK_EVT_FEAT_C3STOP unconditionally
Date: Mon, 5 Oct 2015 18:37:04 +0200 [thread overview]
Message-ID: <5612A730.5030400@sigmadesigns.com> (raw)
In-Reply-To: <5612649C.5020401@sigmadesigns.com>
On 05/10/2015 13:53, Marc Gonzalez wrote:
> In 5388a6b266 ("ARM: SMP: Always enable clock event broadcast support")
> Russell noted that "the TWD local timers are unable to wake up the CPU
> when it is placed into a low power mode".
>
> However, some platforms do not stop the TWD block in low-power mode,
> and can thus use the TWD timer in one-shot mode, without setting up
> a broadcast device.
>
> Make the driver check for the "twd-never-stops" boolean property,
> and set the CLOCK_EVT_FEAT_C3STOP flag accordingly.
>
> Signed-off-by: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
> ---
> Documentation/devicetree/bindings/arm/twd.txt | 4 ++++
> arch/arm/kernel/smp_twd.c | 5 ++++-
> 2 files changed, 8 insertions(+), 1 deletion(-)
Sorry, I don't fully understand the submission process.
Should I now submit my patch to the patch queue?
http://www.arm.linux.org.uk/developer/patches/
Regards.
next prev parent reply other threads:[~2015-10-05 16:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 8:58 [PATCH] twd: Don't set CLOCK_EVT_FEAT_C3STOP unconditionally Marc Gonzalez
2015-10-05 9:17 ` [PATCH v2] " Marc Gonzalez
2015-10-05 9:22 ` Linus Walleij
2015-10-05 9:50 ` [PATCH v3] " Marc Gonzalez
2015-10-05 10:35 ` Mark Rutland
2015-10-05 11:53 ` [PATCH v4] " Marc Gonzalez
2015-10-05 16:37 ` Marc Gonzalez [this message]
2015-10-07 12:14 ` Marc Gonzalez
2015-10-08 17:16 ` Mark Rutland
2015-10-08 17:38 ` Mason
2015-10-08 17:43 ` Russell King - ARM Linux
2015-10-08 18:16 ` Mason
2015-10-08 18:22 ` Russell King - ARM Linux
2015-10-08 18:37 ` Mason
2015-10-08 17:57 ` Mark Rutland
2015-10-08 18:25 ` Mason
2015-10-08 18:34 ` Mark Rutland
2015-10-09 9:29 ` Marc Gonzalez
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=5612A730.5030400@sigmadesigns.com \
--to=marc_gonzalez@sigmadesigns.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).