Thermal Management Kernel Notification
How best to detect thermal event; currently do polling. Use uevent or other system notification (kernel-
Some silicon on-die sensor (for certain OMAP4) contains an interrupt that is generated on any thermal event. This interrupt could be used to trigger the thermal algorithms.
Blueprint information
- Status:
- Complete
- Approver:
- Steve Jahnke
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Steve Jahnke
- Definition:
- Approved
- Series goal:
- Accepted for trunk
- Implementation:
-
Informational
- Milestone target:
-
2011.06
- Started by
- Amit Kucheria
- Completed by
- Amit Kucheria
Related branches
Related bugs
Sprints
Whiteboard
RESULT:
All user-space governors will be able to use the sysfs abstraction provided for by the thermal framework to perform its tasks. A default governor must be provided for in the kernel to handle conditions where the user-space governor is either starved, dies, etc., and should at a minimum prevent an overheating condition to occur. No additional kernel-level information is required to be exported at this time.
[sjahnke] How best to handle the hardware interrupt in a panic condition: DONE
RESULT:
The hardware or firmware (bootloader or ROM code) is responsible for catching and handling the final thermal overload panic condition as the kernel may be compromised in a thermal panic condition; it is best not to have any software dependency in this. If the thermal framework is active when a thermal overheating event occurs, it may soft-reset the device, but the final hardware fail-safe must reset the system independently
Work Items
Work items:
[sjahnke] Determine if there is anything required to get user-space governors into the thermal framework: DONE
Dependency tree
* Blueprints in grey have been implemented.
