diff options
author | Sean Anderson <sean.anderson@linux.dev> | 2024-08-12 17:51:28 -0400 |
---|---|---|
committer | Michal Simek <michal.simek@amd.com> | 2024-10-02 09:21:26 +0200 |
commit | d57df7a7b78eecfe65cb358faf27ad5872bd297f (patch) | |
tree | 638aa8684571b26b4fba7d2c10da473a0975e0ae /tools/perf/scripts/python/syscall-counts.py | |
parent | e279e4b2faf81eb5570138eb61f2c8acd95ce893 (diff) |
arm64: zynqmp: Add thermal zones
Add some thermal trip points. We can't undervolt the CPUs to save power
when we underclock them, so there isn't really a point in throttling
them until we are about to overheat. As such, the passive trip point is
right below the critical trip point.
The critical trip point is the extended/industrial-grade maximum
junction temperature of 100C minus the maximum temperature sensor error
of 3.5C (in the range -55C to 110C). Automotive- and military-grade
parts can go up to 125C, but as far as I can tell there is no way to
detect them at runtime. Userspace can adjust the trip points at runtime,
but this may not be viable when booting above 100C. I think it's
reasonable to ask automotive/military users to edit their device trees
to bump the trip points, but if that proves to be an issue we can
always go with no default temperatures. However, that wouldn't be too
nice for the majority of extended/industrial users.
Signed-off-by: Sean Anderson <sean.anderson@linux.dev>
Link: https://lore.kernel.org/r/20240812215129.3599832-4-sean.anderson@linux.dev
Signed-off-by: Michal Simek <michal.simek@amd.com>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions