On Thu, Jul 31, 2014 at 12:10:40AM +0100, Matt Longnecker wrote: > Some hardware can react autonomously at a programmed temperature. > For example, an SoC might implement a last ditch throttle or a > hardware thermal shutdown. The driver for such a device can > register itself as a cooling_device with the thermal framework. > > With this change, the thermal framework notifies such a driver > when userspace alters the relevant trip temperature so that > the driver can reprogram its hardware
Why can't you just use the existing cooling device interface? Cooling devices can be bound to trip points. Most thermal governors will increase cooling for that cooling device when the trip point is hit. The last ditch throttle or hardware thermal shutdown will then kick when the cooling state changes to 1. If the existing governors are too complex for what you want, you can have a look at the bang bang governor[0] which (I think) is bound to be merged soon. [0] http://article.gmane.org/gmane.linux.kernel/1753348 Cheers, Javi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
