diff options
| author | Peng Fan <peng.fan@nxp.com> | 2021-12-01 20:50:30 +0800 |
|---|---|---|
| committer | Daniel Lezcano <daniel.lezcano@linaro.org> | 2021-12-14 10:17:27 +0100 |
| commit | 0ed9e4ebcebcb36bd1186e68cf2f72b3e0bfbac6 (patch) | |
| tree | c927bc8084cb9313bdc6e24d41df381d95a801da /drivers/clocksource | |
| parent | f5bd5fc9d478cdb94f89ccc74870dd81d1919b42 (diff) | |
| download | linux-0ed9e4ebcebcb36bd1186e68cf2f72b3e0bfbac6.tar.gz linux-0ed9e4ebcebcb36bd1186e68cf2f72b3e0bfbac6.tar.bz2 linux-0ed9e4ebcebcb36bd1186e68cf2f72b3e0bfbac6.zip | |
clocksource/drivers/timer-imx-sysctr: Set cpumask to cpu_possible_mask
The syctr interrupt could set the affinity to any cores in the
SoC. However, the default affinity is set to cpu 0.
This timer will be used as broadcast timer on all the i.MX
SoCs. Because DYNIRQ flag is set, the core time framework will runtime
set the interrupt affinity to the cores that needs to wake up and the
cpumask will runtime set to the core that will be wake up. So even the
sysctr initialization use cpumask 0, there is no issue, the current
patch is just use cpu_possible_mask to show the fact that the timer
supports routed to all the cpu cores and nothing else.
Signed-off-by: Peng Fan <peng.fan@nxp.com>
Link: https://lore.kernel.org/r/20211201125030.2307746-2-peng.fan@oss.nxp.com
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Diffstat (limited to 'drivers/clocksource')
| -rw-r--r-- | drivers/clocksource/timer-imx-sysctr.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/clocksource/timer-imx-sysctr.c b/drivers/clocksource/timer-imx-sysctr.c index 2b309af11266..55a8e198d2a1 100644 --- a/drivers/clocksource/timer-imx-sysctr.c +++ b/drivers/clocksource/timer-imx-sysctr.c @@ -119,7 +119,7 @@ static struct timer_of to_sysctr = { static void __init sysctr_clockevent_init(void) { - to_sysctr.clkevt.cpumask = cpumask_of(0); + to_sysctr.clkevt.cpumask = cpu_possible_mask; clockevents_config_and_register(&to_sysctr.clkevt, timer_of_rate(&to_sysctr), |