summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/timer
diff options
context:
space:
mode:
authorSudeep Holla <sudeep.holla@arm.com>2018-07-11 14:24:22 +0300
committerDaniel Lezcano <daniel.lezcano@linaro.org>2018-07-26 12:26:30 +0300
commitf8f5fe86f7e10ecc784b53537edbe3fcf0c00884 (patch)
tree84a4baeee102c9fb7196e5ab6de0c5de09ec871e /Documentation/devicetree/bindings/timer
parente5af5ff34cf037ac7bb70976161427dc40bf4a96 (diff)
downloadlinux-f8f5fe86f7e10ecc784b53537edbe3fcf0c00884.tar.xz
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 'Documentation/devicetree/bindings/timer')
0 files changed, 0 insertions, 0 deletions