There is an GPIO signal Overtemp_n (pin L52) which has NO linux device-tree binding. From devkit schematic, it seems connect to MCU to perform a force shutdown on overheated.
But since there is no device-tree definition for it, is this Overtemp_n managed by Linux? Or is it managed by BPMP? Or something else? And how is it managed?
you may enable tegrastats utility to reports memory usage and processor usage for Jetson-based devices. or, there’s another utility, JTop for system monitoring.
both of them are reported from the internal thermal sensors.
please also check developer guide, Thermal Management, for more details.
The question is specific about who is driving Overtemp_n pin? L52: TEGRA_MAIN_GPIO(N, 2). I don’t find answer in thermal mgmt page.
- NVIDIA linux thermal driver driving Overtemp_n pin? There has to be a device-tree binding for this GPIO pin (otherwise it is not good linux driver programming practice). But I don’t find it.
- Some NVIDIA user space software driving this pin? But those software are not open source, so I don’t know whether it is this case or not.
- BPMP directly driving Overtemp_n pin?
it should be
TEGRA194_MAIN_GPIO(port, offset) for the Jetson Xavier series.
please also check the header file for definition,
there’s no device tree definition to use this pin,
Thanks for your reply. Yes, I do mean
TEGRA194_MAIN_GPIO. I double checked the pinmux spreadsheet for this pin.
It is pin L52, so
Then it comes back to my question. Who is controlling this pin in software? Please read my question carefully.
had you check developer guide for the details of Jetson Xavier’s Thermal Management ?
you may review thermal framework architecture.