Re: Thermal notifications without setting thermal governor to userspace?

[Chris Down <chris@chrisdown.name>]

Hey Daniel,

Thanks a lot for getting back!

Daniel Lezcano writes:
>For that it would require to setup a trip point from the firmware 
>dedicated to userspace management along with the writable trip point 
>kernel config option.
>
>On embedded systems, the trip point can be added easily in the device tree.
>
>You would end up with:
>
> - one passive trip point : writable and used by userspace
>
> - one passive trip point to protect the system tied with a cooling 
>device and handled by the kernel
>
> - one hot trip point to notify the userspace critical is about to be reach
>
> - one critical trip point to reboot the system
>
>From the userspace, you change the trip temp to 50°C, 70°C and 90°C 
>when crossing the way up or the way down.
>
>The sensor should implement the set_trip in order to program the 
>register to fire the interrupt at the specified temperature. 
>Otherwise, monitoring will be needed.
>
>On ACPI, except hacking the table and reload from the kernel I don't 
>see how to do that.

In my case I'm dealing with "normal" desktop machines and a distribution 
kernel, so it isn't possible to have fine grained control over the kernel 
configuration or device tree (especially since ideally this would be 
usable as an unprivileged user).

Is it still possible to use this in such a scenario?