summaryrefslogtreecommitdiffstats
path: root/drivers/clocksource/timer-keystone.c
diff options
context:
space:
mode:
authorSudeep Holla <sudeep.holla@arm.com>2018-07-11 12:24:22 +0100
committerDaniel Lezcano <daniel.lezcano@linaro.org>2018-07-26 11:26:30 +0200
commitf8f5fe86f7e10ecc784b53537edbe3fcf0c00884 (patch)
tree84a4baeee102c9fb7196e5ab6de0c5de09ec871e /drivers/clocksource/timer-keystone.c
parente5af5ff34cf037ac7bb70976161427dc40bf4a96 (diff)
downloadlinux-f8f5fe86f7e10ecc784b53537edbe3fcf0c00884.tar.gz
linux-f8f5fe86f7e10ecc784b53537edbe3fcf0c00884.tar.bz2
linux-f8f5fe86f7e10ecc784b53537edbe3fcf0c00884.zip
clocksource/drivers: Set clockevent device cpumask to cpu_possible_mask
Currently, quite a few clockevent devices have cpumask set to cpu_all_mask which should be fine. However, cpu_possible_mask is more accurate and if there are any other clockevent devices in the system which have cpumask set to cpu_possible_mask, then having cpu_all_mask may result in issues (mostly boot hang with forever loops in clockevents_notify_released). So, lets replace all the clockevent device cpu_all_mask to cpu_possible_mask in order to prevent above mentioned possible issue. Cc: Daniel Lezcano <daniel.lezcano@linaro.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Thierry Reding <thierry.reding@gmail.com> Cc: Jonathan Hunter <jonathanh@nvidia.com> Cc: Santosh Shilimkar <ssantosh@kernel.org> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Diffstat (limited to 'drivers/clocksource/timer-keystone.c')
-rw-r--r--drivers/clocksource/timer-keystone.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/clocksource/timer-keystone.c b/drivers/clocksource/timer-keystone.c
index 0eee03250cfc..f5b2eda30bf3 100644
--- a/drivers/clocksource/timer-keystone.c
+++ b/drivers/clocksource/timer-keystone.c
@@ -211,7 +211,7 @@ static int __init keystone_timer_init(struct device_node *np)
event_dev->set_state_shutdown = keystone_shutdown;
event_dev->set_state_periodic = keystone_set_periodic;
event_dev->set_state_oneshot = keystone_shutdown;
- event_dev->cpumask = cpu_all_mask;
+ event_dev->cpumask = cpu_possible_mask;
event_dev->owner = THIS_MODULE;
event_dev->name = TIMER_NAME;
event_dev->irq = irq;