[lkml]   [2011]   [Jan]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRE: Thermal kernel events API to userspace - Was: Re: thermal: Avoid CONFIG_NET compile dependency
    Hi Thomas,

    > I wonder which events would need userspace to take specific
    > (configured) actions at all and what kind of action it could be.
    > What is THERMAL_USER_AUX0?
    > When will it get thrown and what is userspace expected to do?

    This THERMAL_USER_AUX0 is meant for the DTS core thresholds.
    In ACPI compliant systems, There are two core thresholds, that
    Can be programmed and read via IA32_THERM_INTERRUPT MSR. One is the
    Lower threshold (AUX0) and the other one is the higher threshold(AUX1).

    When the Current temperature goes below the lower threshold, or above
    the higher threshold, the HW generates an interrupt. This is what is
    forwarded to the user space through the netlink events.

    The user app can increase performance(increase CPU speed..)
    on receiving AUX0 events, and try to reduce performance
    (like CPU frequency reduction, display control..)on getting AUX1 events.
    Basically, the app can do anything to reduce the temperature of the

     \ /
      Last update: 2011-01-25 12:21    [W:0.021 / U:107.696 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site