mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xiubo Li <Li.Xiubo@freescale.com>
To: <daniel.lezcano@linaro.org>, <tglx@linutronix.de>
Cc: <linux-kernel@vger.kernel.org>, Xiubo Li <Li.Xiubo@freescale.com>
Subject: [PATCHv2 3/4] Clocksource: Flextimer: Set cpumask to cpu_possible_mask
Date: Fri, 5 Sep 2014 13:02:19 +0800	[thread overview]
Message-ID: <1409893340-30027-4-git-send-email-Li.Xiubo@freescale.com> (raw)
In-Reply-To: <1409893340-30027-1-git-send-email-Li.Xiubo@freescale.com>

The Flextimer is not tied to CPU0, make it usable on any CPU.
For Vybrid there is only one CPU, while for LS1+ there are more
than one.

Signed-off-by: Xiubo Li <Li.Xiubo@freescale.com>
---
 drivers/clocksource/fsl_ftm_timer.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/clocksource/fsl_ftm_timer.c b/drivers/clocksource/fsl_ftm_timer.c
index ccb8c32..c0ce603 100644
--- a/drivers/clocksource/fsl_ftm_timer.c
+++ b/drivers/clocksource/fsl_ftm_timer.c
@@ -214,7 +214,7 @@ static int __init ftm_clockevent_init(unsigned long freq, int irq)
 		return err;
 	}
 
-	ftm_clockevent.cpumask = cpumask_of(0);
+	ftm_clockevent.cpumask = cpu_all_mask;
 	ftm_clockevent.irq = irq;
 
 	clockevents_config_and_register(&ftm_clockevent,
-- 
2.1.0.27.g96db324


  parent reply	other threads:[~2014-09-05  6:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05  5:02 [PATCHv2 0/4] Clocksource: Flextimer: add LS1 support Xiubo Li
2014-09-05  5:02 ` [PATCHv2 1/4] Clocksource: Flextimer: Use internal clocksource read API Xiubo Li
2014-09-05 15:40   ` Thomas Gleixner
2014-09-09  1:55     ` Li.Xiubo
2014-09-05  5:02 ` [PATCHv2 2/4] Clocksource: Flextimer: Remove the useless code Xiubo Li
2014-09-05  5:02 ` Xiubo Li [this message]
2014-09-05  5:02 ` [PATCHv2 4/4] Clocksource: Flextimer: Fix counter clock prescaler calculation Xiubo Li

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=1409893340-30027-4-git-send-email-Li.Xiubo@freescale.com \
    --to=li.xiubo@freescale.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®