clocksource/drivers: Set clockevent device cpumask to cpu_possible_mask
authorSudeep Holla <sudeep.holla@arm.com>
Wed, 11 Jul 2018 11:24:22 +0000 (12:24 +0100)
committerDaniel Lezcano <daniel.lezcano@linaro.org>
Thu, 26 Jul 2018 09:26:30 +0000 (11:26 +0200)
commitf8f5fe86f7e10ecc784b53537edbe3fcf0c00884
tree84a4baeee102c9fb7196e5ab6de0c5de09ec871e
parente5af5ff34cf037ac7bb70976161427dc40bf4a96
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>
drivers/clocksource/tegra20_timer.c
drivers/clocksource/timer-atcpit100.c
drivers/clocksource/timer-keystone.c
drivers/clocksource/zevio-timer.c