1. 28 Jan, 2004 5 commits
    • Len Brown's avatar
      Merge intel.com:/home/lenb/src/linux-acpi-test-2.6.1 · 3b699911
      Len Brown authored
      into intel.com:/home/lenb/src/linux-acpi-test-2.6.2
      3b699911
    • Len Brown's avatar
      Merge intel.com:/home/lenb/src/linux-acpi-test-2.6.0 · e0654edf
      Len Brown authored
      into intel.com:/home/lenb/src/linux-acpi-test-2.6.1
      e0654edf
    • Dominik Brodowski's avatar
      [ACPI] update _PPC handling -- from Dominik Brodowski · b65fa0c7
      Dominik Brodowski authored
      updates the _PPC handling. It is handled as a CPUfreq
      policy notifier which adjusts the maximum CPU speed
      according to the current platform limit.
      b65fa0c7
    • Dominik Brodowski's avatar
      [ACPI] remove unnecessary check in acpi-cpufreq driver · 987865cc
      Dominik Brodowski authored
      from Dominik Brodowski
      
      The acpi cpufreq driver includes a test at startup which detects whether
      ACPI P-States are supported on any CPU, and whether transitions work.
      However, this test is faulty: it is only run _after_ the acpi driver is
      registered, causing race situations. Also, it doesn't save anything _as_ the
      driver is already registered. So, it can safely be removed.
      987865cc
    • Dominik Brodowski's avatar
      [ACPI] update passive cooling algorithm · 08e90ccc
      Dominik Brodowski authored
      	from Dominik Brodowski
      
      The current algorithm used by Linux ACPI for passive thermal management has
      two shortcomings:
      
      - if increasing the CPU processing power as a thermal situation goes away,
        throttling states are decreased later than performance states. This is
        not wise -- it should be the opposite ordering of going "up".
      
      - only if the ACPI CPUfreq driver is used, performance states are used.
        A generalized approach would offer passive cooling even if the ACPI
        P-States cpufreq driver cannot be used (faulty BIOS, FixedHW access, etc.)
      08e90ccc
  2. 27 Jan, 2004 5 commits
  3. 26 Jan, 2004 23 commits
  4. 25 Jan, 2004 3 commits
  5. 24 Jan, 2004 4 commits