summaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/interrupt-controller/mediatek,sysirq.txt
diff options
context:
space:
mode:
authorViresh Kumar <viresh.kumar@linaro.org>2018-11-16 15:31:12 +0530
committerMatthias Brugger <matthias.bgg@gmail.com>2019-01-09 18:17:39 +0100
commit34948b77bb09b8ad3b3365c3b2b87278ce4473de (patch)
tree761fa25cb44ce19312146649aea73567cd0eee02 /Documentation/devicetree/bindings/interrupt-controller/mediatek,sysirq.txt
parentbfeffd155283772bbe78c6a05dec7c0128ee500c (diff)
downloadlinux-stable-34948b77bb09b8ad3b3365c3b2b87278ce4473de.tar.gz
linux-stable-34948b77bb09b8ad3b3365c3b2b87278ce4473de.tar.bz2
linux-stable-34948b77bb09b8ad3b3365c3b2b87278ce4473de.zip
ARM: dts: mt7623: Add all CPUs in cooling maps
Each CPU can (and does) participate in cooling down the system but the DT only captures a handful of them, normally CPU0, in the cooling maps. Things work by chance currently as under normal circumstances its the first CPU of each cluster which is used by the operating systems to probe the cooling devices. But as soon as this CPU ordering changes and any other CPU is used to bring up the cooling device, we will start seeing failures. Also the DT is rather incomplete when we list only one CPU in the cooling maps, as the hardware doesn't have any such limitations. Update cooling maps to include all devices affected by individual trip points. Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
Diffstat (limited to 'Documentation/devicetree/bindings/interrupt-controller/mediatek,sysirq.txt')
0 files changed, 0 insertions, 0 deletions