SUPERH platform development
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Magnus Damm <magnus.damm@gmail.com>, linux-kernel@vger.kernel.org
Cc: linux-sh@vger.kernel.org, horms@verge.net.au,
	geert@linux-m68k.org, laurent.pinchart@ideasonboard.com,
	tglx@linutronix.de
Subject: Re: [PATCH] clocksource: sh_tmu: Set cpu_possible_mask to fix SMP broadcast
Date: Tue, 16 Dec 2014 11:14:40 +0000	[thread overview]
Message-ID: <54901420.50403@linaro.org> (raw)
In-Reply-To: <20141216094854.22639.69181.sendpatchset@w520>

On 12/16/2014 10:48 AM, Magnus Damm wrote:
> From: Magnus Damm <damm+renesas@opensource.se>
>
> Update the TMU driver to use cpu_possible_mask as cpumask to make
> r8a7779 SMP work as expected with or without the ARM TWD timer.
>
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>

Applied as a 3.18 fix.

Thanks !

   -- Daniel

ps: May I suggest to use the CLOCK_EVT_FEAT_DYNIRQ flag for this driver ?

> ---
>
>   drivers/clocksource/sh_tmu.c |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- 0001/drivers/clocksource/sh_tmu.c
> +++ work/drivers/clocksource/sh_tmu.c	2014-12-16 17:49:49.000000000 +0900
> @@ -428,7 +428,7 @@ static void sh_tmu_register_clockevent(s
>   	ced->features = CLOCK_EVT_FEAT_PERIODIC;
>   	ced->features |= CLOCK_EVT_FEAT_ONESHOT;
>   	ced->rating = 200;
> -	ced->cpumask = cpumask_of(0);
> +	ced->cpumask = cpu_possible_mask;
>   	ced->set_next_event = sh_tmu_clock_event_next;
>   	ced->set_mode = sh_tmu_clock_event_mode;
>   	ced->suspend = sh_tmu_clock_event_suspend;
>


-- 
  <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


  reply	other threads:[~2014-12-16 11:14 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16  9:48 [PATCH] clocksource: sh_tmu: Set cpu_possible_mask to fix SMP broadcast Magnus Damm
2014-12-16 11:14 ` Daniel Lezcano [this message]
2014-12-16 11:20   ` Laurent Pinchart
2014-12-16 11:25     ` Laurent Pinchart
2014-12-16 11:29     ` Daniel Lezcano
2014-12-16 11:46     ` Magnus Damm
2014-12-16 11:54       ` Daniel Lezcano
2014-12-17  0:44         ` Laurent Pinchart
2014-12-16 12:40       ` Geert Uytterhoeven
2014-12-17  1:30         ` Magnus Damm
2014-12-17  2:08           ` Laurent Pinchart
2014-12-17  8:30             ` Geert Uytterhoeven
2014-12-17  9:42               ` Geert Uytterhoeven
2014-12-17 12:04                 ` Laurent Pinchart
2014-12-17 12:11                   ` Geert Uytterhoeven
2014-12-17 12:14                     ` Laurent Pinchart
2014-12-17 11:31               ` Laurent Pinchart
2014-12-17 13:23             ` Magnus Damm
2014-12-19  0:03             ` Magnus Damm
2014-12-19  0:46               ` Laurent Pinchart
2014-12-17  8:25           ` Geert Uytterhoeven
2014-12-17  0:43       ` Laurent Pinchart
2014-12-17 13:59 ` Geert Uytterhoeven
2014-12-17 14:43 ` Laurent Pinchart
2014-12-17 15:34 ` Laurent Pinchart
2014-12-17 15:44 ` Geert Uytterhoeven
2014-12-17 15:46 ` Magnus Damm
2014-12-18  3:29 ` Laurent Pinchart

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=54901420.50403@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.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