From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Simon Horman <horms@verge.net.au>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-kernel@vger.kernel.org, linux@arm.linux.org.uk,
arnd@arndb.de, linux-sh@vger.kernel.org, sboyd@codeaurora.org,
rob.herring@calxeda.com, olof@lixom.net,
santosh.shilimkar@ti.com, grant.likely@linaro.org,
tglx@linutronix.de
Subject: Re: [PATCH] clocksource: em_sti: Set cpu_possible_mask to fix SMP broadcast
Date: Wed, 04 Sep 2013 08:44:18 +0000 [thread overview]
Message-ID: <5226F2E2.3070202@linaro.org> (raw)
In-Reply-To: <20130904083727.GE17329@verge.net.au>
On 09/04/2013 10:37 AM, Simon Horman wrote:
> [ Droped johnstultz@linaro.org CC, the address seems to bounce
The address is john.stultz@linaro.org
> Added Daniel Lezcano CC, I believe he handles clocksource these days ]
Right.
> On Wed, Sep 04, 2013 at 05:01:51PM +0900, Magnus Damm 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>
>
> I will let this sit for a few days to see if there is any further feedback.
>
>> ---
>>
>> Thanks to feedback from Stephen Boyd this is is a reworked version of:
>> [PATCH] clocksource: em_sti: Adjust clock event rating to fix SMP broadcast
>>
>> drivers/clocksource/em_sti.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> --- 0001/drivers/clocksource/em_sti.c
>> +++ work/drivers/clocksource/em_sti.c 2013-09-04 16:51:42.000000000 +0900
>> @@ -301,7 +301,7 @@ static void em_sti_register_clockevent(s
>> ced->name = dev_name(&p->pdev->dev);
>> ced->features = CLOCK_EVT_FEAT_ONESHOT;
>> ced->rating = 200;
>> - ced->cpumask = cpumask_of(0);
>> + ced->cpumask = cpu_possible_mask;
>> ced->set_next_event = em_sti_clock_event_next;
>> ced->set_mode = em_sti_clock_event_mode;
>>
>>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2013-09-04 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130904080151.24562.91334.sendpatchset@w520>
2013-09-04 8:31 ` [PATCH] clocksource: em_sti: Set cpu_possible_mask to fix SMP broadcast Simon Horman
2013-09-04 8:37 ` Simon Horman
2013-09-04 8:44 ` Daniel Lezcano [this message]
2013-09-04 16:29 ` Stephen Boyd
2013-09-05 7:33 ` Simon Horman
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
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=5226F2E2.3070202@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=arnd@arndb.de \
--cc=grant.likely@linaro.org \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=olof@lixom.net \
--cc=rob.herring@calxeda.com \
--cc=santosh.shilimkar@ti.com \
--cc=sboyd@codeaurora.org \
--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).