summaryrefslogtreecommitdiffstats
path: root/arch/arm64/boot/dts/nvidia
diff options
context:
space:
mode:
authorMiquel Raynal <miquel.raynal@bootlin.com>2019-05-21 16:25:04 +0200
committerGregory CLEMENT <gregory.clement@bootlin.com>2019-06-03 16:41:30 +0200
commitfe7f7f229f0705301f6ff44d56375217f0a573f4 (patch)
tree8818c5d7d9847d328ac3c0f0000db2b1e8d55be7 /arch/arm64/boot/dts/nvidia
parentarm64: dts: marvell: Change core numbering in AP806 thermal-node (diff)
downloadlinux-fe7f7f229f0705301f6ff44d56375217f0a573f4.tar.xz
linux-fe7f7f229f0705301f6ff44d56375217f0a573f4.zip
arm64: dts: marvell: Enable AP806 thermal throttling with CPUfreq
Avoid critical temperatures in the AP806 by adding the relevant trip points/cooling-maps using CPUfreq as cooling device. So far, when the temperature reaches 100°C in the thermal IP of the AP806 (close enough from the 2/4 cores) an overheat interrupt is raised. The thermal core then shutdowns the system to avoid damaging the hardware. Adding CPUfreq as a cooling device could help avoiding such very critical situation. For that, we enable thermal throttling by defining, for each CPU, two trip points with the corresponding cooling 'intensity'. CPU0 and CPU1 are in the same cluster and are driven by the same clock. Same applies for CPU2 and CPU3, if available. So changing the frequency of one will also change the frequency of the other one, hence the use of two cooling devices per core. The heat map is as follow: - Below 85°C: the cluster runs at the highest frequency (e.g: 1200MHz). - Between 85°C and 95°C: there are two trip points at half (e.g: 600MHz) and a third (e.g: 400MHz) of the highest frequency. - Above 95°C the cluster runs at a quarter of the highest frequency (e.g: 300MHz). - At 100°C the platform is shutdown. Suggested-by: Omri Itach <omrii@marvell.com> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com> Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
Diffstat (limited to 'arch/arm64/boot/dts/nvidia')
0 files changed, 0 insertions, 0 deletions