-
The previous commit removed per-CPU thermal zones. Despite having a thermal sensor per-CPU, the trip points in those zones would affect *several* CPUs: this system doesn't have per-CPU DVFS, so one cannot change the frequency of an individual CPU, but rather a group thereof (i.e. the frequency domain). Furthermore, the (existing) CPU cluster thermal zones have a "hot" trip point set at the same trip temperature as the lower per-CPU thermal zones. AIUI this is actually useless, as the struct thermal_zone_device_ops provided by thermal_of.c doesn't contain a .notify() callback, so no action will (and can) be taken as a consequence of hitting that trip point. Copy the previous per-CPU trip points / cooling maps into the CPU cluster thermal zones. This should effectively lead to a similar CPU thermal management as before with less overhead. Signed-off-by: Valentin Schneider <valentin.schneider@arm.com>
78f50df5