linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] clocksource: em_sti: Set cpu_possible_mask to fix SMP broadcast
Date: Wed, 25 Sep 2013 23:43:21 +0000	[thread overview]
Message-ID: <20130925234321.GF20882@verge.net.au> (raw)
In-Reply-To: <52435348.30008@linaro.org>

On Wed, Sep 25, 2013 at 11:19:04PM +0200, Daniel Lezcano wrote:
> On 09/18/2013 10:01 PM, Simon Horman wrote:
> > From: Magnus Damm <damm@opensource.se>
> > 
> > Update the STI driver by setting cpu_possible_mask to make EMEV2
> > SMP work as expected together with the ARM broadcast timer.
> > 
> > This breakage was introduced by:
> > 
> > f7db706 ARM: 7674/1: smp: Avoid dummy clockevent being preferred over real hardware clock-event
> > 
> > Without this fix SMP operation is broken on EMEV2 since no
> > broadcast timer interrupts trigger on the secondary CPU cores.
> > 
> > Signed-off-by: Magnus Damm <damm@opensource.se>
> > Tested-by: Simon Horman <horms+renesas@verge.net.au>
> > Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
> > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> > ---
> 
> Thanks ! Applied to my tree as 3.12 fix.

Thanks!

  reply	other threads:[~2013-09-25 23:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18 20:01 [PATCH] Renesas clocksource fixes for v3.12 Simon Horman
2013-09-18 20:01 ` [PATCH] clocksource: em_sti: Set cpu_possible_mask to fix SMP broadcast Simon Horman
2013-09-25 21:19   ` Daniel Lezcano
2013-09-25 23:43     ` Simon Horman [this message]
     [not found] <20130904080151.24562.91334.sendpatchset@w520>
2013-09-04  8:31 ` Simon Horman
2013-09-04  8:37 ` Simon Horman
2013-09-04  8:44   ` Daniel Lezcano
2013-09-04 16:29     ` Stephen Boyd
2013-09-05  7:33       ` Simon Horman

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=20130925234321.GF20882@verge.net.au \
    --to=horms@verge.net.au \
    --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).