1. 07 May, 2004 11 commits
    • Dave Jones's avatar
      [CPUFREQ] Add p4-clockmod ->get · 8a92d663
      Dave Jones authored
      p4-clockmod is a bit more complicated as it might run on SMP, HT, and
      the instructions need to run on the specific (physical) CPU.
      8a92d663
    • Dave Jones's avatar
      [CPUFREQ] Add longrun ->get · 0344b7bf
      Dave Jones authored
      Longrun users might be interested in their CPU's current frequency as
      well, so use a longrun-specific cpuid-call in longrun_get().
      0344b7bf
    • Dave Jones's avatar
      [CPUFREQ] Add a longhaul_get function. · 573cb858
      Dave Jones authored
      573cb858
    • Dave Jones's avatar
      e31c257d
    • Dave Jones's avatar
      cc2adf35
    • Dave Jones's avatar
      [CPUFREQ] Handle CPUFREQ_RESUMECHANGE notifications · 4f111beb
      Dave Jones authored
      Notifications in i386, sparc64, x86_64, sh-sci and sa11xx-pcmcia notifiers.
      sa1100-framebuffer doesn't seem to be able to handle frequency transitions
      behind its back well. So, sa11xx will be marked
      CPUFREQ_PANIC_OUTOFSYNC | CPUFREQ_PANIC_RESUME_OUTOFSYNC later.
      4f111beb
    • Dave Jones's avatar
      [CPUFREQ] (Hopefully) fix cpufreq resume support. · ceccad84
      Dave Jones authored
       
      Upon resuming, first CPUfreq hardware support needs to be re-enabled in certain cases
      (call to cpufreq_driver->resume()).
       
      Then, two different paths may need to be taken:
      a) frequency during suspend equals frequency during resume ==> everything is fine,
       
      b) frequency differ ==> either we can't handle it, then panic (see flag
         CPUFREQ_PANIC_RESUME_OUTOFSYNC). Or we can handle it, then notify all
      ceccad84
    • Dave Jones's avatar
      [CPUFREQ] Fix 'out of sync' issue. · 6a4a93f9
      Dave Jones authored
      Sometimes we might discover during a call to cpufreq_get() that we're "out of sync",
      meaning the actual CPU frequency changed "behind our back". If this happens, the flag
      CPUFREQ_PANIC_OUTOFSYNC decides what can be done: if it is set, the kernel panic's,
      it it is not set, the cpufreq transition notifiers are informed of this change, and
      a call to cpufreq_update_policy() is scheduled [using the default workqueue] so that
      the user-defined values override BIOS / external interaction.
      6a4a93f9
    • Dave Jones's avatar
      [CPUFREQ] Export cpufreq_get() to userspace. · 98525f6f
      Dave Jones authored
      As it involves calls to hardware which might take some time,
      only let the super-user read out this value.
      98525f6f
    • Dave Jones's avatar
      [CPUFREQ] Move cpufreq_get() from the userspace governor to the core. · 657b1437
      Dave Jones authored
      Contrary to the previous implementation, it now calls the cpufreq driver,
      and reads out the _actual_ current frequency, and not the frequency the
      CPUfreq core _thinks_ the CPU is running at. Most cpufreq drivers do provide
      such a "hw get" function (only ACPI-io can definitely not be supported,
      I'm not sure about sh, sparc64 and powermac) anyway, and it is useful for
      other issues.
      657b1437
    • Dave Jones's avatar
      [CPUFREQ] Export scaling cur frequencies · f962f4e7
      Dave Jones authored
      Many users want to know the current cpu freqeuncy, even if not using
      the userspace frequency. On ->target cpufreq drivers (if they do their
      calls to cpufreq_notify_transition correctly) this just means reading
      out cpufreq_policy->cur.
      f962f4e7
  2. 22 Apr, 2004 3 commits
  3. 21 Apr, 2004 5 commits
  4. 19 Apr, 2004 3 commits
  5. 16 Apr, 2004 1 commit
  6. 14 Apr, 2004 11 commits
  7. 13 Apr, 2004 6 commits