1. 12 Aug, 2007 3 commits
    • Len Brown's avatar
      ACPI: thermal: create "thermal.psv=" to override passive trip points · a70cdc52
      Len Brown authored
      
      "thermal.psv=-1" disables passive trip points
      for all ACPI thermal zones.
      
      "thermal.psv=C", where 'C' is degrees Celsius,
      overrides all existing passive trip points
      for all ACPI thermal zones.
      
      thermal.psv is checked at module load time,
      and in response to trip-point change events.
      
      Note that if the system does not deliver thermal zone
      temperature change events near the new trip-point,
      then it will not be noticed.  To force your custom
      trip point to be noticed, you may need to enable polling:
      eg. thermal.tzp=3000 invokes polling every 5 minutes.
      
      Note that once passive thermal throttling is invoked,
      it has its own internal Thermal Sampling Period (_TSP),
      that is unrelated to _TZP.
      
      WARNING: disabling or raising a thermal trip point
      may result in increased running temperature and
      shorter hardware lifetime on some systems.
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      a70cdc52
    • Len Brown's avatar
      ACPI: thermal: expose "thermal.tzp=" to set global polling frequency · 730ff34d
      Len Brown authored
      
      Thermal Zone Polling frequency (_TZP) is an optional ACPI object
      recommending the rate that the OS should poll the associated thermal zone.
      
      If _TZP is 0, no polling should be used.
      If _TZP is non-zero, then the platform recommends that
      the OS poll the thermal zone at the specified rate.
      The minimum period is 30 seconds.
      The maximum period is 5 minutes.
      
      (note _TZP and thermal.tzp units are in deci-seconds,
       so _TZP = 300 corresponds to 30 seconds)
      
      If _TZP is not present, ACPI 3.0b recommends that the
      thermal zone be polled at an "OS provided default frequency".
      
      However, common industry practice is:
      1. The BIOS never specifies any _TZP
      2. High volume OS's from this century never poll any thermal zones
      
      Ie. The OS depends on the platform's ability to
      provoke thermal events when necessary, and
      the "OS provided default frequency" is "never":-)
      
      There is a proposal that ACPI 4.0 be updated to reflect
      common industry practice -- ie. no _TZP, no polling.
      
      The Linux kernel already follows this practice --
      thermal zones are not polled unless _TZP is present and non-zero.
      
      But thermal zone polling is useful as a workaround for systems
      which have ACPI thermal control, but have an issue preventing
      thermal events.  Indeed, some Linux distributions still
      set a non-zero thermal polling frequency for this reason.
      
      But rather than ask the user to write a polling frequency
      into all the /proc/acpi/thermal_zone/*/polling_frequency
      files, here we simply document and expose the already
      existing module parameter to do the same at system level,
      to simplify debugging those broken platforms.
      
      Note that thermal.tzp is a module-load time parameter only.
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      730ff34d
    • Len Brown's avatar
      ACPI: thermal: create "thermal.off=1" to disable ACPI thermal support · 72b33ef8
      Len Brown authored
      
      "thermal.off=1" disables all ACPI thermal support at boot time.
      
      CONFIG_ACPI_THERMAL=n can do this at build time.
      "# rmmod thermal" can do this at run time,
      as long as thermal is built as a module.
      
      WARNING: On some systems, disabling ACPI thermal support
      will cause the system to run hotter and reduce the
      lifetime of the hardware.
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      72b33ef8
  2. 23 Jul, 2007 1 commit
  3. 18 Jul, 2007 1 commit
    • Jeremy Fitzhardinge's avatar
      Add common orderly_poweroff() · 10a0a8d4
      Jeremy Fitzhardinge authored
      
      Various pieces of code around the kernel want to be able to trigger an
      orderly poweroff.  This pulls them together into a single
      implementation.
      
      By default the poweroff command is /sbin/poweroff, but it can be set
      via sysctl: kernel/poweroff_cmd.  This is split at whitespace, so it
      can include command-line arguments.
      
      This patch replaces four other instances of invoking either "poweroff"
      or "shutdown -h now": two sbus drivers, and acpi thermal
      management.
      
      sparc64 has its own "powerd"; still need to determine whether it should
      be replaced by orderly_poweroff().
      Signed-off-by: default avatarJeremy Fitzhardinge <jeremy@xensource.com>
      Acked-by: default avatarLen Brown <lenb@kernel.org>
      Signed-off-by: default avatarChris Wright <chrisw@sous-sol.org>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: Randy Dunlap <randy.dunlap@oracle.com>
      Cc: Andi Kleen <ak@suse.de>
      Cc: Al Viro <viro@zeniv.linux.org.uk>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: David S. Miller <davem@davemloft.net>
      10a0a8d4
  4. 18 Jun, 2007 1 commit
  5. 29 May, 2007 1 commit
  6. 30 Apr, 2007 2 commits
    • Len Brown's avatar
      ACPI: delete un-reliable concept of cooling mode · eaca2d3f
      Len Brown authored
      
      The scheme where the thermal driver displayed the
      cooling mode /proc/acpi/thermal_zone/*/cooling_mode
      was flawed in two ways.
      
      First, the success of _SCP doesn't actually mean
      that the BIOS moved any trip points.
      On many BIOS, _SCP is present, but does nothing.
      So displaying what _SCP executed actually
      was wrong more times than it was right.
      
      Second, examining the relative position of the
      trip points when the thermal_zone is added
      is insufficient -- as the BIOS reserves the right
      to change the trip points at run-time.
      
      The only reliable way for the user to determine if
      the thermal zone is in active, passive, or critical
      mode is to examine the relative position of the trip points.
      The user can do this without the kernel doing it
      for them by looking in /proc/acpi/thermal_zone/*/trip_points
      
      New contents for /proc/acpi/thermal_zone/*/cooling_mode:
      
      If _SCP available:
      "0 - Active; 1 - Passive\n"
      
      If _SCP unavailable:
      "<setting not supported>\n"
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      eaca2d3f
    • Len Brown's avatar
      ACPI: thermal trip points are read-only · 11ccc0f2
      Len Brown authored
      
      /proc/acpi/thermal_zone/*/trip_points displays
      what the kernel reads from the BIOS via ACPI.
      
      If you echo a string of ':' deliminted numbers to this file
      then it will change what it displays.
      
      But it shouldn't, since the kernel has no way to communicate
      these changes to ACPI thermal zones.  ACPI thermal zone
      trip points are read-only.
      
      The kernel does have the opportunity to ask the BIOS to change
      the trip points with _SCP - Set Cooling Policy.
      
      Request Active Cooling Mode:
      # echo 0 > /proc/acpi/thermal_zone/*/cooling_policy
      
      Request Passive Cooling Mode:
      # echo 1 > /proc/acpi/thermal_zone/*/cooling_policy
      
      However, in practice it is quite rare for the BIOS
      to support the optional _SCP, and it is even more rare
      for the BIOS to export an _SCP that actually changes
      the trip points.
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      11ccc0f2
  7. 24 Apr, 2007 1 commit
  8. 16 Feb, 2007 2 commits
  9. 14 Feb, 2007 1 commit
    • Tim Schmielau's avatar
      [PATCH] remove many unneeded #includes of sched.h · cd354f1a
      Tim Schmielau authored
      
      After Al Viro (finally) succeeded in removing the sched.h #include in module.h
      recently, it makes sense again to remove other superfluous sched.h includes.
      There are quite a lot of files which include it but don't actually need
      anything defined in there.  Presumably these includes were once needed for
      macros that used to live in sched.h, but moved to other header files in the
      course of cleaning it up.
      
      To ease the pain, this time I did not fiddle with any header files and only
      removed #includes from .c-files, which tend to cause less trouble.
      
      Compile tested against 2.6.20-rc2 and 2.6.20-rc2-mm2 (with offsets) on alpha,
      arm, i386, ia64, mips, powerpc, and x86_64 with allnoconfig, defconfig,
      allmodconfig, and allyesconfig as well as a few randconfigs on x86_64 and all
      configs in arch/arm/configs on arm.  I also checked that no new warnings were
      introduced by the patch (actually, some warnings are removed that were emitted
      by unnecessarily included header files).
      Signed-off-by: default avatarTim Schmielau <tim@physik3.uni-rostock.de>
      Acked-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      cd354f1a
  10. 12 Feb, 2007 3 commits
    • Len Brown's avatar
      ACPI: delete extra #defines in /drivers/acpi/ drivers · 7cda93e0
      Len Brown authored
      
      Cosmetic only.
      
      Except in a single case, #define ACPI_*_DRIVER_NAME
      were invoked 0 or 1 times.
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      7cda93e0
    • Len Brown's avatar
      ACPI: fix acpi_driver.name usage · c2b6705b
      Len Brown authored
      
      It was erroneously used as a description rather than a name.
      
      ie. turn this:
      
      lenb@se7525gp2:/sys> ls bus/acpi/drivers
      ACPI AC Adapter Driver  ACPI Embedded Controller Driver  ACPI Power Resource Driver
      ACPI Battery Driver     ACPI Fan Driver                  ACPI Processor Driver
      ACPI Button Driver      ACPI PCI Interrupt Link Driver   ACPI Thermal Zone Driver
      ACPI container driver   ACPI PCI Root Bridge Driver      hpet
      
      into this:
      
      lenb@se7525gp2:~> ls /sys/bus/acpi/drivers
      ac  battery  button  container  ec  fan  hpet  pci_link  pci_root  power  processor  thermal
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      c2b6705b
    • Len Brown's avatar
      ACPI: clean up ACPI_MODULE_NAME() use · f52fd66d
      Len Brown authored
      
      cosmetic only
      
      Make "module name" actually match the file name.
      Invoke with ';' as leaving it off confuses Lindent and gcc doesn't care.
      Fix indentation where Lindent did get confused.
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      f52fd66d
  11. 20 Dec, 2006 1 commit
  12. 15 Dec, 2006 1 commit
  13. 14 Oct, 2006 1 commit
  14. 10 Jul, 2006 2 commits
  15. 30 Jun, 2006 3 commits
  16. 27 Jun, 2006 3 commits
  17. 26 Jun, 2006 1 commit
  18. 14 Jun, 2006 1 commit
  19. 15 May, 2006 1 commit
  20. 13 May, 2006 1 commit
  21. 31 Mar, 2006 1 commit
  22. 30 Nov, 2005 1 commit
  23. 05 Aug, 2005 1 commit
  24. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4