03 Aug, 2011

1 commit

  • THERMAL_HWMON is implemented inside the thermal_sys driver and has no
    effect on drivers implementing thermal zones, so they shouldn't see
    anything related to it in . Making the THERMAL_HWMON
    implementation fully internal has two advantages beyond the cleaner
    design:

    * This avoids rebuilding all thermal drivers if the THERMAL_HWMON
    implementation changes, or if CONFIG_THERMAL_HWMON gets enabled or
    disabled.

    * This avoids breaking the thermal kABI in these cases too, which should
    make distributions happy.

    The only drawback I can see is slightly higher memory fragmentation, as
    the number of kzalloc() calls will increase by one per thermal zone. But
    I doubt it will be a problem in practice, as I've never seen a system with
    more than two thermal zones.

    Signed-off-by: Jean Delvare
    Cc: Rene Herman
    Acked-by: Guenter Roeck
    Signed-off-by: Andrew Morton
    Signed-off-by: Len Brown

    Jean Delvare
     

01 Mar, 2011

1 commit

  • Several ACPI drivers fail to build if CONFIG_NET is unset, because
    they refer to things depending on CONFIG_THERMAL that in turn depends
    on CONFIG_NET. However, CONFIG_THERMAL doesn't really need to depend
    on CONFIG_NET, because the only part of it requiring CONFIG_NET is
    the netlink interface in thermal_sys.c.

    Put the netlink interface in thermal_sys.c under #ifdef CONFIG_NET
    and remove the dependency of CONFIG_THERMAL on CONFIG_NET from
    drivers/thermal/Kconfig.

    Signed-off-by: Rafael J. Wysocki
    Acked-by: Randy Dunlap
    Cc: Ingo Molnar
    Cc: Len Brown
    Cc: Stephen Rothwell
    Cc: Luming Yu
    Cc: Andrew Morton
    Signed-off-by: Linus Torvalds

    Rafael J. Wysocki
     

12 Jan, 2011

2 commits


01 Dec, 2010

1 commit


28 Mar, 2009

1 commit

  • Due to poor thermal design or Linux driving hardware outside its thermal
    envelope, some systems will reach critical temperature and shut down
    under high load. This patch adds support for forcing a polling-based
    passive trip point if the firmware doesn't provide one. The assumption
    is made that the processor is the most practical means to reduce the
    dynamic heat generation, so hitting the passive thermal limit will cause
    the CPU to be throttled until the temperature stabalises around the
    defined value.

    UI is provided via a "passive" sysfs entry in the thermal zone
    directory. It accepts a decimal value in millidegrees celsius, or "0" to
    disable the functionality. Default behaviour is for this functionality
    to be disabled.

    Signed-off-by: Matthew Garrett
    Signed-off-by: Len Brown

    Matthew Garrett
     

21 Feb, 2009

1 commit


20 Feb, 2009

1 commit


26 Jun, 2008

1 commit


29 Apr, 2008

3 commits


16 Apr, 2008

1 commit

  • The THERMAL_MAX_TRIPS value is set to 10. It is too few for the Compaq AP550
    machine which has 12 trip points.

    Signed-off-by: Krzysztof Helt
    Cc: Len Brown
    Cc: Zhang Rui
    Cc: "Rafael J. Wysocki"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Krzysztof Helt
     

09 Feb, 2008

1 commit


02 Feb, 2008

2 commits