Linux CPU Freq
[Prev Page][Next Page]
- Re: [PATCH v4 0/8] cpufreq: use cpufreq-cpu0 driver for exynos based platforms
- From: Arnd Bergmann <arnd@xxxxxxxx>
- Re: [PATCH v4 7/8] ARM: Exynos: switch to using generic cpufreq-cpu0 driver
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v4 7/8] ARM: Exynos: switch to using generic cpufreq-cpu0 driver
- From: Heiko Stübner <heiko@xxxxxxxxx>
- Re: [PATCH v4 0/8] cpufreq: use cpufreq-cpu0 driver for exynos based platforms
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v4 7/8] ARM: Exynos: switch to using generic cpufreq-cpu0 driver
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v4 0/8] cpufreq: use cpufreq-cpu0 driver for exynos based platforms
- From: Arnd Bergmann <arnd@xxxxxxxx>
- Re: [PATCH v4 7/8] ARM: Exynos: switch to using generic cpufreq-cpu0 driver
- From: Arnd Bergmann <arnd@xxxxxxxx>
- Re: [PATCH v4 8/8] cpufreq: exynos: remove all exynos specific cpufreq driver support
- From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
- Re: [PATCH v4 1/8] cpufreq: cpufreq-cpu0: allow use of optional boost mode frequencies
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v4 1/8] cpufreq: cpufreq-cpu0: allow use of optional boost mode frequencies
- From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
- Re: [PATCH v4 8/8] cpufreq: exynos: remove all exynos specific cpufreq driver support
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v4 2/8] clk: samsung: change scope of samsung clock lock to global
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v4 1/8] cpufreq: cpufreq-cpu0: allow use of optional boost mode frequencies
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH v4 8/8] cpufreq: exynos: remove all exynos specific cpufreq driver support
- From: Thomas Abraham <ta.omasab@xxxxxxxxx>
- [PATCH v4 7/8] ARM: Exynos: switch to using generic cpufreq-cpu0 driver
- From: Thomas Abraham <ta.omasab@xxxxxxxxx>
- [PATCH v4 6/8] ARM: dts: Exynos: add cpu nodes, opp and cpu clock configuration data
- From: Thomas Abraham <ta.omasab@xxxxxxxxx>
- [PATCH v4 5/8] clk: exynos: use cpu-clock provider type to represent arm clock.
- From: Thomas Abraham <ta.omasab@xxxxxxxxx>
- [PATCH v4 4/8] Documentation: devicetree: add cpu clock configuration data binding for Exynos4/5
- From: Thomas Abraham <ta.omasab@xxxxxxxxx>
- [PATCH v4 3/8] clk: samsung: add infrastructure to register cpu clocks
- From: Thomas Abraham <ta.omasab@xxxxxxxxx>
- [PATCH v4 2/8] clk: samsung: change scope of samsung clock lock to global
- From: Thomas Abraham <ta.omasab@xxxxxxxxx>
- [PATCH v4 1/8] cpufreq: cpufreq-cpu0: allow use of optional boost mode frequencies
- From: Thomas Abraham <ta.omasab@xxxxxxxxx>
- [PATCH v4 0/8] cpufreq: use cpufreq-cpu0 driver for exynos based platforms
- From: Thomas Abraham <ta.omasab@xxxxxxxxx>
- Re: [PATCH 0/2] PM / OPP: move cpufreq specific helpers out of OPP layer
- From: Thomas Abraham <ta.omasab@xxxxxxxxx>
- Re: [PATCH] cpufreq: powernv: make local function static
- From: Gautham R Shenoy <ego@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: powernv: make local function static
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: powernv: make local function static
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- [Bug 72361] AMD APU reset infinite
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 72361] AMD APU reset infinite
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 72361] AMD APU reset infinite
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 72361] AMD APU reset infinite
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [PATCH] cpufreq: powernv: make local function static
- From: Brian Norris <computersforpeace@xxxxxxxxx>
- [Bug 65671] hibernation - IO errors writing to swap, crashing apps, 3,11.8 worked, unless rmmod powernow_k8
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH] cpufreq: Break out early when frequency equals target_freq
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH v5 0/8] Introduce new cpufreq helper macros
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- [Bug 75661] acpi-cpufreq cannot use lowest reported P-state (A8-4500M)
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75661] New: acpi-cpufreq cannot use lowest reported P-state
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: Performance regression in v3.14
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [PATCH v5 0/8] Introduce new cpufreq helper macros
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v5 0/8] Introduce new cpufreq helper macros
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH v5 0/8] Introduce new cpufreq helper macros
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: Performance regression in v3.14
- From: Romain Francoise <romain@xxxxxxxxxxxxx>
- Re: Performance regression in v3.14
- From: Johan Hovold <jhovold@xxxxxxxxx>
- Re: Performance regression in v3.14
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v5 0/8] Introduce new cpufreq helper macros
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v5 0/8] Introduce new cpufreq helper macros
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Performance regression in v3.14
- From: Johan Hovold <jhovold@xxxxxxxxx>
- Re: [PATCH v5 0/8] Introduce new cpufreq helper macros
- From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH 1/2] PM / OPP: Remove cpufreq wrapper dependency on internal data organization
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/2] PM / OPP: Move cpufreq specific OPP functions out of generic OPP library
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/2] PM / OPP: Remove cpufreq wrapper dependency on internal data organization
- From: Nishanth Menon <nm@xxxxxx>
- Re: [PATCH 1/2] PM / OPP: Remove cpufreq wrapper dependency on internal data organization
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 0/2] PM / OPP: move cpufreq specific helpers out of OPP layer
- From: Nishanth Menon <nm@xxxxxx>
- [PATCH 1/2] PM / OPP: Remove cpufreq wrapper dependency on internal data organization
- From: Nishanth Menon <nm@xxxxxx>
- [PATCH 2/2] PM / OPP: Move cpufreq specific OPP functions out of generic OPP library
- From: Nishanth Menon <nm@xxxxxx>
- Re: time_in_state on Ubuntu 13.10
- From: Mascha Kurpicz <mascha.kurpicz@xxxxxxxx>
- Re: [PATCH v3] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH v3] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end
- From: Meelis Roos <mroos@xxxxxxxx>
- [PATCH v3] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH v2] cpufreq: intel_pstate: Change the calculation of next pstate
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [RFC PATCH] PM / OPP: move cpufreq specific OPP functions out of generic OPP library
- From: Nishanth Menon <nm@xxxxxx>
- Re: [PATCH v2] cpufreq: intel_pstate: Change the calculation of next pstate
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: time_in_state on Ubuntu 13.10
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [RFC PATCH] PM / OPP: move cpufreq specific OPP functions out of generic OPP library
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [RFC PATCH] PM / OPP: move cpufreq specific OPP functions out of generic OPP library
- From: Nishanth Menon <nm@xxxxxx>
- Re: [RFC PATCH] PM / OPP: move cpufreq specific OPP functions out of generic OPP library
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v2] cpufreq: intel_pstate: Change the calculation of next pstate
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- [RFC PATCH] PM / OPP: move cpufreq specific OPP functions out of generic OPP library
- From: Nishanth Menon <nm@xxxxxx>
- Re: [PATCH v2] cpufreq: intel_pstate: Change the calculation of next pstate
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH v2] cpufreq: intel_pstate: Change the calculation of next pstate
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- [PATCH v2] cpufreq: intel_pstate: Change the calculation of next pstate
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH] cpufreq: intel_pstate: Change the calculation of next pstate
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [PATCH] cpufreq: intel_pstate: Remove sample parameter in intel_pstate_calc_busy
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- [Bug 65671] hibernation - IO errors writing to swap, crashing apps, 3,11.8 worked, unless rmmod powernow_k8
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 65671] hibernation - IO errors writing to swap, crashing apps, 3,11.8 worked, unless rmmod powernow_k8
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH] cpufreq: powernow-k8: Fix checkpatch warnings
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH v5 0/8] Introduce new cpufreq helper macros
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH 2/3] cpufreq: Removed exynos_sort_descend_freq_table funtion
- From: Jonghwan Choi <jhbird.choi@xxxxxxxxxxx>
- [PATCH 3/3] cpufreq: Pass third argument as function parameter is
- From: Jonghwan Choi <jhbird.choi@xxxxxxxxxxx>
- Re: [PATCH] cpufreq: intel_pstate: Remove sample parameter in intel_pstate_calc_busy
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: powernow-k8: Fix checkpatch warnings
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 75121] New: Intel Pstate driver - powersave mode - CPU frequency too low
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH] cpufreq: powernow-k8: Fix checkpatch warnings
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: intel_pstate: Disable interrupts during MSRs reading
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH v5 0/8] Introduce new cpufreq helper macros
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: intel_pstate: Change the calculation of next pstate
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- [PATCH] cpufreq: Break out early when frequency equals target_freq
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH] cpufreq: intel_pstate: Remove sample parameter in intel_pstate_calc_busy
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH] cpufreq: intel_pstate: Disable interrupts during MSRs reading
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH] cpufreq: intel_pstate: Change the calculation of next pstate
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH v5 0/8] Introduce new cpufreq helper macros
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH v2] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v2] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH v2] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end
- From: Meelis Roos <mroos@xxxxxxxx>
- [PATCH v2] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: time_in_state on Ubuntu 13.10
- From: Mascha Kurpicz <mascha.kurpicz@xxxxxxxx>
- Re: time_in_state on Ubuntu 13.10
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v2 5/5] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH v2 5/5] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v2 5/5] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: time_in_state on Ubuntu 13.10
- From: Mascha Kurpicz <mascha.kurpicz@xxxxxxxx>
- RE: [PATCH 2/2] cpufreq: Remove exynos_sort_descend_freq_table in exynos5440-cpufreq.c
- From: Jonghwan Choi <jhbird.choi@xxxxxxxxxxx>
- Re: [PATCH v2 5/5] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/2] cpufreq: Remove exynos_sort_descend_freq_table in exynos5440-cpufreq.c
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v2 5/5] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH 2/2] cpufreq: Remove exynos_sort_descend_freq_table in exynos5440-cpufreq.c
- From: Amit Kachhap <amit.kachhap@xxxxxxxxx>
- Re: [PATCH v2 5/5] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH v2 0/5] Cpufreq frequency serialization fixes
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH 2/2] cpufreq: Remove exynos_sort_descend_freq_table in exynos5440-cpufreq.c
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 2/2] cpufreq: Remove exynos_sort_descend_freq_table in exynos5440-cpufreq.c
- From: Jonghwan Choi <jhbird.choi@xxxxxxxxxxx>
- Re: [PATCH] cpufreq: intel_pstate: Change the calculation of next pstate
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v2 5/5] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v2 5/5] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: time_in_state on Ubuntu 13.10
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v5 0/8] Introduce new cpufreq helper macros
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v2 0/5] Cpufreq frequency serialization fixes
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH v2 0/5] Cpufreq frequency serialization fixes
- From: Meelis Roos <mroos@xxxxxxxx>
- [PATCH v2 0/5] Cpufreq frequency serialization fixes
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- [PATCH v2 1/5] cpufreq, longhaul: Fix double invocation of cpufreq_freq_transition_begin/end
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- [PATCH v2 3/5] cpufreq, powernow-k6: Fix double invocation of cpufreq_freq_transition_begin/end
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- [PATCH v2 5/5] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- [PATCH v2 4/5] cpufreq, powernow-k7: Fix double invocation of cpufreq_freq_transition_begin/end
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- [PATCH v2 2/5] cpufreq, powernow-k6: Fix incorrect comparison with max_multipler
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH 0/3] Cpufreq frequency serialization fixes
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- time_in_state on Ubuntu 13.10
- From: Mascha Kurpicz <mascha.kurpicz@xxxxxxxx>
- [PATCH] cpufreq: intel_pstate: Change the calculation of next pstate
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH v5 2/8] cpufreq: Use cpufreq_for_each_* macros for frequency table iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH v5 2/8] cpufreq: Use cpufreq_for_each_* macros for frequency table iteration
- From: Prabhakar Lad <prabhakar.csengg@xxxxxxxxx>
- [PATCH v5 0/8] Introduce new cpufreq helper macros
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH v5 1/8] cpufreq: Introduce macros for cpufreq_frequency_table iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH v5 2/8] cpufreq: Use cpufreq_for_each_* macros for frequency table iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH 0/3] Cpufreq frequency serialization fixes
- From: Meelis Roos <mroos@xxxxxxxx>
- Re: [PATCH v4 2/8] cpufreq: Use cpufreq_for_each_* macros for frequency table iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH v4 2/8] cpufreq: Use cpufreq_for_each_* macros for frequency table iteration
- From: Prabhakar Lad <prabhakar.csengg@xxxxxxxxx>
- Re: [PATCH 2/3] cpufreq, powernow-k6: Fix double invocation of cpufreq_freq_transition_begin/end
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/3] cpufreq, longhaul: Fix double invocation of cpufreq_freq_transition_begin/end
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/3] cpufreq, longhaul: Fix double invocation of cpufreq_freq_transition_begin/end
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/3] cpufreq, powernow-k6: Fix double invocation of cpufreq_freq_transition_begin/end
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 1/3] cpufreq, longhaul: Fix double invocation of cpufreq_freq_transition_begin/end
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- [PATCH 0/3] Cpufreq frequency serialization fixes
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH 3/3] cpufreq, powernow-k7: Fix double invocation of cpufreq_freq_transition_begin/end
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: Set CPUFREQ_ASYNC_NOTIFICATION for drivers handling notification
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- [PATCH 2/3] cpufreq, powernow-k6: Fix double invocation of cpufreq_freq_transition_begin/end
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- [PATCH 3/3] cpufreq, powernow-k7: Fix double invocation of cpufreq_freq_transition_begin/end
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: 3.15-rc2: longhaul cpufreq stalls tasks for 120s+
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- [PATCH] cpufreq: Set CPUFREQ_ASYNC_NOTIFICATION for drivers handling notification
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: 3.15-rc2: longhaul cpufreq stalls tasks for 120s+
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: 3.15-rc2: longhaul cpufreq stalls tasks for 120s+
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: 3.15-rc2: longhaul cpufreq stalls tasks for 120s+
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: 3.15-rc2: longhaul cpufreq stalls tasks for 120s+
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: 3.15-rc2: longhaul cpufreq stalls tasks for 120s+
- From: Meelis Roos <mroos@xxxxxxxx>
- [PATCH] cpupower, add option to display frequencies and latencies without rounding off values
- From: Prarit Bhargava <prarit@xxxxxxxxxx>
- Re: 3.15-rc2: longhaul cpufreq stalls tasks for 120s+
- From: Meelis Roos <mroos@xxxxxxxx>
- Re: 3.15-rc2: longhaul cpufreq stalls tasks for 120s+
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: 3.15-rc2: longhaul cpufreq stalls tasks for 120s+
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: 3.15-rc2: longhaul cpufreq stalls tasks for 120s+
- From: Meelis Roos <mroos@xxxxxxxx>
- 3.15-rc2: longhaul cpufreq stalls tasks for 120s+
- From: Meelis Roos <mroos@xxxxxxxx>
- Re: 3.15-rc2: longhaul cpufreq stalls tasks for 120s+
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: CPUFREQ: Try to load pcc driver on HP ProLiants automatically
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: powernow-k8: Fix checkpatch warnings
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH] cpufreq: powernow-k8: Fix checkpatch warnings
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- CPUFREQ: Try to load pcc driver on HP ProLiants automatically
- From: Thomas Renninger <trenn@xxxxxxx>
- Re: [PATCH] cpufreq: powernow-k8: Fix checkpatch warnings
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: powernow-k8: Fix checkpatch warnings
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: Kconfig: Fix spelling errors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH] cpufreq: powernow-k8: Fix checkpatch warnings
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH] cpufreq: Kconfig: Fix spelling errors
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH] cpufreq: Make linux-pm@xxxxxxxxxxxxxxx official mailing list
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH v4 2/8] cpufreq: Use cpufreq_for_each_* macros for frequency table iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH v4 1/8] cpufreq: Introduce macros for cpufreq_frequency_table iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH RESEND 1/2] cpufreq: imx6q: Drop devm_clk/regulator_get usage
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH v3 1/8] cpufreq: Introduce macros for cpufreq_frequency_table iteration
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: Should we get cpufreq@xxxxxxxxxxxxxxx removed?
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: Another powernow-k6 bug
- From: Ben Hutchings <ben@xxxxxxxxxxxxxxx>
- Re: [PATCH 3/3] cpufreq: ppc: Fix handling of non-existent clocks
- From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
- Re: [PATCH 1/2] cpufreq: exynos: Use dev_err/info function instead of pr_err/info
- From: Chanwoo Choi <cw00.choi@xxxxxxxxxxx>
- Re: [PATCH 1/2] cpufreq: exynos: Use dev_err/info function instead of pr_err/info
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 3/3] cpufreq: ppc: Fix handling of non-existent clocks
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/3] cpufreq: ppc: Fix integer overflow in expression
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/3] cpufreq: ppc: Add missing #include <asm/smp.h>
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Should we get cpufreq@xxxxxxxxxxxxxxx removed?
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: Another powernow-k6 bug
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/2] Support cpufreq driver for Exynos3250
- From: Tomasz Figa <tomasz.figa@xxxxxxxxx>
- Re: [PATCH 0/2] Support cpufreq driver for Exynos3250
- From: Sachin Kamat <sachin.kamat@xxxxxxxxxx>
- Re: [PATCH 0/2] Support cpufreq driver for Exynos3250
- From: Tomasz Figa <tomasz.figa@xxxxxxxxx>
- Re: [PATCH 0/2] Support cpufreq driver for Exynos3250
- From: Chanwoo Choi <cwchoi00@xxxxxxxxx>
- Re: [PATCH 0/2] Support cpufreq driver for Exynos3250
- From: Sachin Kamat <sachin.kamat@xxxxxxxxxx>
- [Bug 64261] Intel Pstate driver truncates to pstate instead of rounding to nearest pstate
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 64251] Intel Pstate driver minimum percent does not change with turbo off
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 65501] Blind angle of 1% between up_threshold and down_threshold
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 72211] intel_pstate Haswell CPU is not entering hardware package idle state
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [PATCH 1/2] cpufreq: exynos: Use dev_err/info function instead of pr_err/info
- From: Chanwoo Choi <cw00.choi@xxxxxxxxxxx>
- [PATCH 2/2] cpufreq: exynos: Add new Exynos3250 cpufreq driver
- From: Chanwoo Choi <cw00.choi@xxxxxxxxxxx>
- [PATCH 0/2] Support cpufreq driver for Exynos3250
- From: Chanwoo Choi <cw00.choi@xxxxxxxxxxx>
- [Bug 73781] acpi-cpufreq cannot be loaded.
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 73781] acpi-cpufreq cannot be loaded.
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 73781] acpi-cpufreq cannot be loaded.
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [PATCH 1/3] cpufreq: ppc: Add missing #include <asm/smp.h>
- From: Geert Uytterhoeven <geert+renesas@xxxxxxxxx>
- [PATCH 3/3] cpufreq: ppc: Fix handling of non-existent clocks
- From: Geert Uytterhoeven <geert+renesas@xxxxxxxxx>
- [PATCH 2/3] cpufreq: ppc: Fix integer overflow in expression
- From: Geert Uytterhoeven <geert+renesas@xxxxxxxxx>
- [Bug 73781] acpi-cpufreq cannot be loaded.
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Another powernow-k6 bug
- From: Ben Hutchings <ben@xxxxxxxxxxxxxxx>
- [Bug 73781] acpi-cpufreq cannot be loaded.
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 73781] acpi-cpufreq cannot be loaded.
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH v2 0/8] Introduce new cpufreq helper macros
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH v3 1/8] cpufreq: Introduce macros for cpufreq_frequency_table iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH v2] cpufreq, powernv: Fix build failure on UP
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH] cpufreq, powernv: Fix build failure on UP
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH] cpufreq, powernv: Fix build failure on UP
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH] cpufreq, powernv: Fix build failure on UP
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH v2 0/8] Introduce new cpufreq helper macros
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v2 1/8] cpufreq: Introduce macros for cpufreq_frequency_table iteration
- From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
- [PATCH v2 1/8] cpufreq: Introduce macros for cpufreq_frequency_table iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH v2 2/8] cpufreq: Use cpufreq_for_each_* macros for frequency table iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH v2 0/8] Introduce new cpufreq helper macros
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH 00/20] Introduce new cpufreq helper macros
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH 08/20] cpufreq: exynos5440: Use cpufreq_for_each_entry macro for iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH 02/20] cpufreq: acpi-cpufreq: Use cpufreq_for_each_entry macro for iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [Bug 64271] Intel Pstate driver - "kick" code is not needed
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 64271] Intel Pstate driver - "kick" code is not needed
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 73421] intel/p_state Does not increase into Turbo Boost states and does not display all governors. i5-3201M
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH 00/20] Introduce new cpufreq helper macros
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [Bug 73741] intel_pstate.c does not support scaling_cur_freq and breaks gkrellm-gkfreq monitor
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH 09/20] cpufreq: longhaul: Use cpufreq_for_each_entry macro for iteration
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 08/20] cpufreq: exynos5440: Use cpufreq_for_each_entry macro for iteration
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 07/20] cpufreq: exynos: Use cpufreq_for_each_entry macro for iteration
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 05/20] cpufreq: dbx500: Use cpufreq_for_each_entry macro for iteration
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 03/20] cpufreq: stats: Use cpufreq_for_each_valid_entry macro for iteration
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 02/20] cpufreq: acpi-cpufreq: Use cpufreq_for_each_entry macro for iteration
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 01/20] cpufreq: Introduce macros for cpufreq_frequency_table iteration
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 01/20] cpufreq: Introduce macros for cpufreq_frequency_table iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH 02/20] cpufreq: acpi-cpufreq: Use cpufreq_for_each_entry macro for iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH 03/20] cpufreq: stats: Use cpufreq_for_each_valid_entry macro for iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH 04/20] cpufreq: arm_big_little: Use cpufreq_for_each_entry macro for iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH 05/20] cpufreq: dbx500: Use cpufreq_for_each_entry macro for iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH 06/20] cpufreq: elanfreq: Use cpufreq_for_each_entry macro for iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH 07/20] cpufreq: exynos: Use cpufreq_for_each_entry macro for iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH 08/20] cpufreq: exynos5440: Use cpufreq_for_each_entry macro for iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH 09/20] cpufreq: longhaul: Use cpufreq_for_each_entry macro for iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH 10/20] cpufreq: powernow-k6: Use cpufreq_for_each_entry macro for iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH 11/20] cpufreq: s3c2416: Use cpufreq_for_each_valid_entry macro for iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH 12/20] cpufreq: s3c64xx: Use cpufreq_for_each_valid_entry macro for iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH 19/20] cpufreq: pcc_cbe: Use cpufreq_for_each_entry macro for iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH 18/20] cpufreq: pasemi: Use cpufreq_for_each_entry macro for iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH 00/20] Introduce new cpufreq helper macros
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH RESEND 2/2] cpufreq: imx6q: Remove unused include
- From: Philipp Zabel <p.zabel@xxxxxxxxxxxxxx>
- [PATCH RESEND 1/2] cpufreq: imx6q: Drop devm_clk/regulator_get usage
- From: Philipp Zabel <p.zabel@xxxxxxxxxxxxxx>
- Re: [RFC PATCH] cpufreq: Introduce macros for cpufreq_frequency_table iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [stable request <=3.7] acpi-cpufreq: set current frequency based on target P-State
- From: Greg KH <greg@xxxxxxxxx>
- [Bug 73781] acpi-cpufreq cannot be loaded.
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 73781] acpi-cpufreq cannot be loaded.
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 73781] acpi-cpufreq cannot be loaded.
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 73781] acpi-cpufreq cannot be loaded.
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 73781] acpi-cpufreq cannot be loaded.
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 73781] acpi-cpufreq cannot be loaded.
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH] cpufreq: unicore32: replace IS_ERR and PTR_ERR with PTR_ERR_OR_ZERO
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [Bug 73781] acpi-cpufreq cannot be loaded.
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [PATCH] cpufreq: unicore32: replace IS_ERR and PTR_ERR with PTR_ERR_OR_ZERO
- From: Duan Jiong <duanj.fnst@xxxxxxxxxxxxxx>
- Re: [RFC PATCH] cpufreq: Introduce macros for cpufreq_frequency_table iteration
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [Bug 73781] acpi-cpufreq cannot be loaded.
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [RFC PATCH] cpufreq: Introduce macros for cpufreq_frequency_table iteration
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [Bug 73781] acpi-cpufreq cannot be loaded.
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 73781] acpi-cpufreq cannot be loaded.
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 73781] New: acpi-cpufreq cannot be loaded.
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH] cpufreq: highbank: fix ARM_HIGHBANK_CPUFREQ dependency warning
- From: Kefeng Wang <wangkefeng.wang@xxxxxxxxxx>
- Re: [PATCH] cpufreq: highbank: fix ARM_HIGHBANK_CPUFREQ dependency warning
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- [Bug 73741] intel_pstate.c does not support scaling_cur_freq and breaks gkrellm-gkfreq monitor
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH] cpufreq: highbank: fix ARM_HIGHBANK_CPUFREQ dependency warning
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH] cpufreq: highbank: fix ARM_HIGHBANK_CPUFREQ dependency warning
- From: Kefeng Wang <wangkefeng.wang@xxxxxxxxxx>
- Re: [PATCH V2 1/4] cpufreq: ia64: don't set .driver_data to index
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH 1/1] cpufreq: exynos: Disable on multiplatform build
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: at32ap: don't declare local variable as static
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: loongson2_cpufreq: don't declare local variable as static
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH 1/1] cpufreq: ppc: Remove duplicate inclusion of fsl_soc.h
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH] drivers:cpufreq:unicore32: fix typo issue for 'clk'
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH] drivers:cpufreq:unicore32: fix typo issue for 'clk'
- From: Chen Gang <gang.chen.5i5j@xxxxxxxxx>
- Re: [PATCH] drivers:cpufreq:unicore32: fix typo issue for 'clk'
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/1] cpufreq: ppc: Remove duplicate inclusion of fsl_soc.h
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 1/1] cpufreq: ppc: Remove duplicate inclusion of fsl_soc.h
- From: Sachin Kamat <sachin.kamat@xxxxxxxxxx>
- Re: [PATCH] drivers:cpufreq:unicore32: fix typo issue for 'clk'
- From: Chen Gang <gang.chen.5i5j@xxxxxxxxx>
- Re: [PATCH] cpufreq: remove sysfs link when a cpu != policy->cpu, is removed
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] drivers:cpufreq:unicore32: fix typo issue for 'clk'
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- 回复: [PATCH] drivers:cpufreq:unicore32: fix typo issue for 'clk'
- From: 管雪涛 <gxt@xxxxxxxxxx>
- Re: [PATCH] drivers:cpufreq:unicore32: fix typo issue for 'clk'
- From: Chen Gang <gang.chen.5i5j@xxxxxxxxx>
- Re: [PATCH] cpufreq: remove sysfs link when a cpu != policy->cpu, is removed
- From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
- Re: [PATCH] drivers:cpufreq:unicore32: fix typo issue for 'clk'
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH] drivers:cpufreq:unicore32: fix typo issue for 'clk'
- From: Chen Gang <gang.chen.5i5j@xxxxxxxxx>
- Re: [PATCH] cpufreq: loongson2_cpufreq: don't declare local variable as static
- From: Alexandre Oliva <oliva@xxxxxxx>
- [PATCH v2] MIPS/loongson2_cpufreq: fix CPU clock rate setting
- From: Aaro Koskinen <aaro.koskinen@xxxxxx>
- Re: [PATCH] MIPS/loongson2_cpufreq: fix CPU clock rate setting
- From: Aaro Koskinen <aaro.koskinen@xxxxxx>
- [Bug 73421] intel/p_state Does not increase into Turbo Boost states and does not display all governors. i5-3201M
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 73421] intel/p_state Does not increase into Turbo Boost states and does not display all governors. i5-3201M
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH] cpufreq: at32ap: don't declare local variable as static
- From: Hans-Christian Egtvedt <egtvedt@xxxxxxxxxxxx>
- [PATCH] cpufreq: at32ap: don't declare local variable as static
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: loongson2_cpufreq: don't declare local variable as static
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: loongson2_cpufreq: don't declare local variable as static
- From: Alexandre Oliva <oliva@xxxxxxx>
- Re: [PATCH 1/1] cpufreq: exynos: Disable on multiplatform build
- From: Sachin Kamat <sachin.kamat@xxxxxxxxxx>
- Re: [PATCH 0/2] Backport to 3.10 stable (Fix CPU0 stall after CPU1 hotplug)
- From: Luís Henriques <luis.henriques@xxxxxxxxxxxxx>
- Re: [PATCH] arm64: Fix duplicated Kconfig entries again
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] MIPS/loongson2_cpufreq: fix CPU clock rate setting
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [Bug 73421] intel/p_state Does not increase into Turbo Boost states and does not display all governors. i5-3201M
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 73421] intel/p_state Does not increase into Turbo Boost states and does not display all governors. i5-3201M
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 73421] intel/p_state Does not increase into Turbo Boost states and does not display all governors. i5-3201M
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 73421] intel/p_state Does not increase into Turbo Boost states and does not display all governors. i5-3201M
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 73421] New: intel/p_state Does not increase into Turbo Boost states and does not display al governors. i5-3201M
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [PATCH] MIPS/loongson2_cpufreq: fix CPU clock rate setting
- From: Aaro Koskinen <aaro.koskinen@xxxxxx>
- [PATCH] arm64: Fix duplicated Kconfig entries again
- From: Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxx>
- [PATCH 0/2] Backport to 3.10 stable (Fix CPU0 stall after CPU1 hotplug)
- From: Krzysztof Kozlowski <k.kozlowski@xxxxxxxxxxx>
- [PATCH 1/2] cpufreq: Fix governor start/stop race condition
- From: Krzysztof Kozlowski <k.kozlowski@xxxxxxxxxxx>
- [PATCH 2/2] cpufreq: Fix timer/workqueue corruption due to double queueing
- From: Krzysztof Kozlowski <k.kozlowski@xxxxxxxxxxx>
- Re: [PATCH REPOST v5 1/3] powernv, cpufreq: Select CPUFreq related Kconfig options for powernv
- From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/1] cpufreq: exynos: Disable on multiplatform build
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 1/1] cpufreq: exynos: Disable on multiplatform build
- From: Sachin Kamat <sachin.kamat@xxxxxxxxxx>
- Re: [PATCH REPOST v5 1/3] powernv, cpufreq: Select CPUFreq related Kconfig options for powernv
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: arm64/cqufreq Kconfig error with v3.14-3893-gc12e69c6aaf7
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH] cpufreq: loongson2_cpufreq: don't declare local variable as static
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH REPOST v5 1/3] powernv, cpufreq: Select CPUFreq related Kconfig options for powernv
- From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH REPOST v5 1/3] powernv, cpufreq: Select CPUFreq related Kconfig options for powernv
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: cpufrequtils error with Core i7 "Haswell" 4771 on Funtoo Linux
- From: Thomas Renninger <trenn@xxxxxxx>
- Re: [PATCH REPOST v5 1/3] powernv, cpufreq: Select CPUFreq related Kconfig options for powernv
- From: Benjamin Herrenschmidt <benh@xxxxxxxxxxx>
- [PATCH REPOST v5 3/3] powernv,cpufreq: Use cpufreq_frequency_table.driver_data to store pstate ids
- From: "Gautham R. Shenoy" <ego@xxxxxxxxxxxxxxxxxx>
- [PATCH REPOST v5 1/3] powernv, cpufreq: Select CPUFreq related Kconfig options for powernv
- From: "Gautham R. Shenoy" <ego@xxxxxxxxxxxxxxxxxx>
- [PATCH REPOST v5 2/3] powernv, cpufreq: cpufreq driver for powernv platform
- From: "Gautham R. Shenoy" <ego@xxxxxxxxxxxxxxxxxx>
- Re: Why are the file perns of /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq much more rigide ?
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Why are the file perns of /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq much more rigide ?
- From: Toralf Förster <toralf.foerster@xxxxxx>
- Re: [stable request <=3.7] acpi-cpufreq: set current frequency based on target P-State
- From: Luís Henriques <luis.henriques@xxxxxxxxxxxxx>
- Re: [PATCH v5 0/3] powernv,cpufreq: Dynamic Frequency Scaling support
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v5 1/3] powernv, cpufreq: Select CPUFreq related Kconfig options for powernv
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- cpufrequtils error with Core i7 "Haswell" 4771 on Funtoo Linux
- From: Sandro <alcerb1972@xxxxxxxxx>
- Re: Move of powerpc/cell cpufreq drivers
- From: Jean Delvare <jdelvare@xxxxxxx>
- Re: Move of powerpc/cell cpufreq drivers
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: Move of powerpc/cell cpufreq drivers
- From: Arnd Bergmann <arnd@xxxxxxxx>
- [PATCH v5 0/3] powernv,cpufreq: Dynamic Frequency Scaling support
- From: "Gautham R. Shenoy" <ego@xxxxxxxxxxxxxxxxxx>
- [PATCH v5 1/3] powernv, cpufreq: Select CPUFreq related Kconfig options for powernv
- From: "Gautham R. Shenoy" <ego@xxxxxxxxxxxxxxxxxx>
- [PATCH v5 2/3] powernv, cpufreq: cpufreq driver for powernv platform
- From: "Gautham R. Shenoy" <ego@xxxxxxxxxxxxxxxxxx>
- [PATCH v5 3/3] powernv,cpufreq: Use cpufreq_frequency_table.driver_data to store pstate ids
- From: "Gautham R. Shenoy" <ego@xxxxxxxxxxxxxxxxxx>
- Re: Move of powerpc/cell cpufreq drivers
- From: Jean Delvare <jdelvare@xxxxxxx>
- Re: Move of powerpc/cell cpufreq drivers
- From: Arnd Bergmann <arnd@xxxxxxxx>
- [PATCH V2 2/4] cpufreq: don't print value of .driver_data from core
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V2 3/4] cpufreq: use kzalloc() to allocate memory for cpufreq_frequency_table
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V2 4/4] cpufreq: create another field .flags in cpufreq_frequency_table
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V2 1/4] cpufreq: ia64: don't set .driver_data to index
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: use kzalloc() to allocate memory for cpufreq_frequency_table
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: use kzalloc() to allocate memory for cpufreq_frequency_table
- From: Joe Perches <joe@xxxxxxxxxxx>
- Re: [PATCH] cpufreq: use kzalloc() to allocate memory for cpufreq_frequency_table
- From: Gautham R Shenoy <ego@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: create another field .flags in cpufreq_frequency_table
- From: Gautham R Shenoy <ego@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: create another field .flags in cpufreq_frequency_table
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: create another field .flags in cpufreq_frequency_table
- From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
- [PATCH] cpufreq: use kzalloc() to allocate memory for cpufreq_frequency_table
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Move of powerpc/cell cpufreq drivers
- From: Jean Delvare <jdelvare@xxxxxxx>
- Re: [PATCH] cpufreq: set value of CPUFREQ_BOOST_FREQ to 0xABABABAB
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH] cpufreq: create another field .flags in cpufreq_frequency_table
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: don't print value of .driver_data from core
- From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
- Re: [PATCH] cpufreq: don't print value of .driver_data from core
- From: Gautham R Shenoy <ego@xxxxxxxxxxxxxxxxxx>
- [PATCH] cpufreq: ia64: don't set .driver_data to index
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: don't print value of .driver_data from core
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: don't print value of .driver_data from core
- From: Gautham R Shenoy <ego@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: don't print value of .driver_data from core
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- [PATCH] cpufreq: don't print value of .driver_data from core
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [stable request <=3.7] acpi-cpufreq: set current frequency based on target P-State
- From: rosslagerwall@xxxxxxxxx
- Re: [stable request <=3.7] acpi-cpufreq: set current frequency based on target P-State
- From: Vinson Lee <vlee@xxxxxxxxxxxxxxxx>
- Re: [stable request <=3.7] acpi-cpufreq: set current frequency based on target P-State
- From: rosslagerwall@xxxxxxxxx
- [PATCH] acpi-cpufreq: set current frequency based on target P-State
- From: Vinson Lee <vlee@xxxxxxxxxxxxxxxx>
- [stable request <=3.7] acpi-cpufreq: set current frequency based on target P-State
- From: Vinson Lee <vlee@xxxxxxxxxxxxxxxx>
- Re: [PATCH] intel_pstate: Use del_timer_sync in intel_pstate_cpu_stop
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [RFC 2/9] opp-modifier: Add opp-modifier-reg driver
- From: Dave Gerlach <d-gerlach@xxxxxx>
- [Bug 65671] hibernation - IO errors writing to swap, crashing apps, 3,11.8 worked, unless rmmod powernow_k8
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 72211] intel_pstate Haswell CPU is not entering hardware package idle state
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH] intel_pstate: Use del_timer_sync in intel_pstate_cpu_stop
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- [PATCH] intel_pstate: Use del_timer_sync in intel_pstate_cpu_stop
- From: dirk.brandewie@xxxxxxxxx
- Re: [patch 15/16] cpufreq: intel-pstate: Use del_timer_sync in intel_pstate_cpu_exit()
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [RFC v3 0/5] cpufreq:LAB: Support for LAB governor.
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [RFC v3 0/5] cpufreq:LAB: Support for LAB governor.
- From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
- Re: [PATCH] cpufreq: set value of CPUFREQ_BOOST_FREQ to 0xABABABAB
- From: Gautham R Shenoy <ego@xxxxxxxxxxxxxxxxxx>
- Re: [RFC v3 0/5] cpufreq:LAB: Support for LAB governor.
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: set value of CPUFREQ_BOOST_FREQ to 0xABABABAB
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V5 0/3] cpufreq: Introduce cpufreq_freq_transition_{begin|end}()
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: set value of CPUFREQ_BOOST_FREQ to 0xABABABAB
- From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
- [PATCH V5 1/3] cpufreq: Make sure frequency transitions are serialized
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V5 2/3] cpufreq: Convert existing drivers to use cpufreq_freq_transition_{begin|end}
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V5 3/3] cpufreq: Make cpufreq_notify_transition & cpufreq_notify_post_transition static
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V5 0/3] cpufreq: Introduce cpufreq_freq_transition_{begin|end}()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH] cpufreq: resume drivers before enabling governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [RFC v3 0/5] cpufreq:LAB: Support for LAB governor.
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V4 1/3] cpufreq: Make sure frequency transitions are serialized
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- [PATCH] cpufreq: set value of CPUFREQ_BOOST_FREQ to 0xABABABAB
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [RFC v3 0/5] cpufreq:LAB: Support for LAB governor.
- From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
- Re: [PATCH V4 1/3] cpufreq: Make sure frequency transitions are serialized
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [patch 15/16] cpufreq: intel-pstate: Use del_timer_sync in intel_pstate_cpu_exit()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [patch 15/16] cpufreq: intel-pstate: Use del_timer_sync in intel_pstate_cpu_exit()
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- [Bug 58001] "ondemand" CPU governor never raises frequency (Dell XPS 12)
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 58001] "ondemand" CPU governor never raises frequency (Dell XPS 12)
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [patch 15/16] cpufreq: intel-pstate: Use del_timer_sync in intel_pstate_cpu_exit()
- From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
- Re: [PATCH V4 1/3] cpufreq: Make sure frequency transitions are serialized
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V4 1/3] cpufreq: Make sure frequency transitions are serialized
- From: Catalin Marinas <catalin.marinas@xxxxxxx>
- Re: [PATCH V4 1/3] cpufreq: Make sure frequency transitions are serialized
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH V4 1/3] cpufreq: Make sure frequency transitions are serialized
- From: Catalin Marinas <catalin.marinas@xxxxxxx>
- Re: [PATCH V4 1/3] cpufreq: Make sure frequency transitions are serialized
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V4 1/3] cpufreq: Make sure frequency transitions are serialized
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V4 1/3] cpufreq: Make sure frequency transitions are serialized
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH V4 2/3] cpufreq: Convert existing drivers to use cpufreq_freq_transition_{begin|end}
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V4 1/3] cpufreq: Make sure frequency transitions are serialized
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V4 3/3] cpufreq: Make cpufreq_notify_transition & cpufreq_notify_post_transition static
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH V4 2/3] cpufreq: Convert existing drivers to use cpufreq_freq_transition_{begin|end}
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH V4 1/3] cpufreq: Make sure frequency transitions are serialized
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- [PATCH V4 3/3] cpufreq: Make cpufreq_notify_transition & cpufreq_notify_post_transition static
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V4 2/3] cpufreq: Convert existing drivers to use cpufreq_freq_transition_{begin|end}
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V4 1/3] cpufreq: Make sure frequency transitions are serialized
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V4 0/3] cpufreq: Introduce cpufreq_freq_transition_{begin|end}()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [Bug 72211] intel_pstate Haswell CPU is not entering hardware package idle state
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [RFC v3] cpufreq: Make sure frequency transitions are serialized
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [RFC v3] cpufreq: Make sure frequency transitions are serialized
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [RFC v3] cpufreq: Make sure frequency transitions are serialized
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [RFC v3] cpufreq: Make sure frequency transitions are serialized
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [RFC v3] cpufreq: Make sure frequency transitions are serialized
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [RFC v3] cpufreq: Make sure frequency transitions are serialized
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [RFC v3] cpufreq: Make sure frequency transitions are serialized
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: Remove unnecessary braces
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: Fix checkpatch errors and warnings
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: Remove unnecessary braces
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [RFC PATCH 3/6] PM / Voltagedomain: introduce voltage domain driver support
- From: Mike Turquette <mturquette@xxxxxxxxxx>
- Re: [PATCH] cpufreq: Remove unnecessary braces
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- [PATCH] cpufreq: Remove unnecessary braces
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH] cpufreq: Fix checkpatch errors and warnings
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [Bug 72361] AMD APU reset infinite
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 72361] New: AMD APU reset infinite
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [RFC v3] cpufreq: Make sure frequency transitions are serialized
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: intel-pstate driver questions
- From: Thomas Renninger <trenn@xxxxxxx>
- Re: [RFC v3] cpufreq: Make sure frequency transitions are serialized
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [RFC V2] cpufreq: make sure frequency transitions are serialized
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [RFC v3] cpufreq: Make sure frequency transitions are serialized
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: remove unused notifier: CPUFREQ_{SUSPENDCHANGE|RESUMECHANGE}
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- [RFC v3] cpufreq: Make sure frequency transitions are serialized
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [RFC V2] cpufreq: make sure frequency transitions are serialized
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [RFC V2] cpufreq: make sure frequency transitions are serialized
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [RFC V2] cpufreq: make sure frequency transitions are serialized
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [RFC V2] cpufreq: make sure frequency transitions are serialized
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [RFC V2] cpufreq: make sure frequency transitions are serialized
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: remove unused notifier: CPUFREQ_{SUSPENDCHANGE|RESUMECHANGE}
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [RFC V2] cpufreq: make sure frequency transitions are serialized
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH] cpufreq: remove unused notifier: CPUFREQ_{SUSPENDCHANGE|RESUMECHANGE}
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- RE: [PATCH] cpufreq: powerpc: replace CPUFREQ_ETERNAL with cpufreq transition latency for FSL e500mc Socs
- From: "Zhuoyu.Zhang@xxxxxxxxxxxxx" <Zhuoyu.Zhang@xxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: powerpc: replace CPUFREQ_ETERNAL with cpufreq transition latency for FSL e500mc Socs
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: intel-pstate driver questions
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- intel-pstate driver questions
- From: Thomas Renninger <trenn@xxxxxxx>
- Re: [RFC 2/9] opp-modifier: Add opp-modifier-reg driver
- From: Nishanth Menon <nm@xxxxxx>
- Re: [RFC V2] cpufreq: make sure frequency transitions are serialized
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: Skip current frequency initialization for ->setpolicy drivers
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [RFC v3 0/5] cpufreq:LAB: Support for LAB governor.
- From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
- Re: [RFC v3 0/5] cpufreq:LAB: Support for LAB governor.
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v2] cpufreq: powerpc: add cpufreq transition latency for FSL e500mc Socs
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH v2] cpufreq: powerpc: add cpufreq transition latency for FSL e500mc Socs
- From: Zhuoyu Zhang <Zhuoyu.Zhang@xxxxxxxxxxxxx>
- RE: [PATCH] cpufreq: powerpc: add cpufreq transition latency for FSL e500mc Socs
- From: "Zhuoyu.Zhang@xxxxxxxxxxxxx" <Zhuoyu.Zhang@xxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: powerpc: add cpufreq transition latency for FSL e500mc Socs
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [RFC 2/9] opp-modifier: Add opp-modifier-reg driver
- From: Rob Herring <robherring2@xxxxxxxxx>
- Re: [RFC v3 0/5] cpufreq:LAB: Support for LAB governor.
- From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
- Re: [RFC 2/9] opp-modifier: Add opp-modifier-reg driver
- From: Nishanth Menon <nm@xxxxxx>
- [PATCH] cpufreq: powerpc: add cpufreq transition latency for FSL e500mc Socs
- From: Zhuoyu Zhang <Zhuoyu.Zhang@xxxxxxxxxxxxx>
- [PATCH] cpufreq: powerpc: replace CPUFREQ_ETERNAL with cpufreq transition latency for FSL e500mc Socs
- From: Zhuoyu Zhang <Zhuoyu.Zhang@xxxxxxxxxxxxx>
- [Bug 71931] intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 72211] New: intel_pstate Haswell CPU is not entering hardware package idle state
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [RFC 2/9] opp-modifier: Add opp-modifier-reg driver
- From: Rob Herring <robherring2@xxxxxxxxx>
- Re: [RFC] cpufreq-cpu0: allow OPP table supplied by platform
- From: Dave Gerlach <d-gerlach@xxxxxx>
- [RFC 2/9] opp-modifier: Add opp-modifier-reg driver
- From: Dave Gerlach <d-gerlach@xxxxxx>
- [RFC 0/9] Introduce OPP modifier for ARM SoCs
- From: Dave Gerlach <d-gerlach@xxxxxx>
- [RFC 7/9] ARM: dts: omap4460: Add opp-modifier entry and add higher OPPs
- From: Dave Gerlach <d-gerlach@xxxxxx>
- [RFC 5/9] ARM: dts: AM4372: Add opp-modifier device entry and add higher OPPs
- From: Dave Gerlach <d-gerlach@xxxxxx>
- [RFC 9/9] ARM: dts: imx6q: Add opp-modifier device entry
- From: Dave Gerlach <d-gerlach@xxxxxx>
- [RFC 6/9] ARM: dts: omap443x: Add opp-modifier entry and add higher OPPs
- From: Dave Gerlach <d-gerlach@xxxxxx>
- [RFC 1/9] opp-modifier: Introduce OPP Modifier Framework
- From: Dave Gerlach <d-gerlach@xxxxxx>
- [RFC 4/9] ARM: dts: AM33XX: Add opp-modifier device entry and add higher OPPs
- From: Dave Gerlach <d-gerlach@xxxxxx>
- [RFC 3/9] PM / OPP: Add hook to modify OPPs after they are loaded.
- From: Dave Gerlach <d-gerlach@xxxxxx>
- [RFC 8/9] ARM: dts: dra7: Add opp-modifier device entry and add higher OPPs
- From: Dave Gerlach <d-gerlach@xxxxxx>
- Re: [RFC] cpufreq-cpu0: allow OPP table supplied by platform
- From: Nishanth Menon <nm@xxxxxx>
- Re: [RFC] cpufreq-cpu0: allow OPP table supplied by platform
- From: Shawn Guo <shawn.guo@xxxxxxxxxxxxx>
- Re: [PATCH 1/2] cpufreq: arm_big_little: make vexpress driver dependent on bL core driver
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- [RFC V2] cpufreq: make sure frequency transitions are serialized
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 2/2] cpufreq: arm_big_little: set 'physical_cluster' for each cpu
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 1/2] cpufreq: arm_big_little: make vexpress driver dependent on bL core driver
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [RFC] cpufreq-cpu0: allow OPP table supplied by platform
- From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
- Re: [RFC] cpufreq-cpu0: allow OPP table supplied by platform
- From: Jisheng Zhang <jszhang@xxxxxxxxxxx>
- Re: [RFC] cpufreq-cpu0: allow OPP table supplied by platform
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [RFC] cpufreq-cpu0: allow OPP table supplied by platform
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [RFC] cpufreq-cpu0: allow OPP table supplied by platform
- From: Jisheng Zhang <jszhang@xxxxxxxxxxx>
- Re: [PATCH] cpufreq: Skip current frequency initialization for ->setpolicy drivers
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- [PATCH] cpufreq: Skip current frequency initialization for ->setpolicy drivers
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- [Bug 71931] intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: Patrik Lundquist <patrik.lundquist@xxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: Patrik Lundquist <patrik.lundquist@xxxxxxxxx>
- [Bug 71931] intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 71931] intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v2] cpufreq: Reformat printk() statements
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- [Bug 71931] intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: Patrik Lundquist <patrik.lundquist@xxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- [Bug 71931] New: intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH v2] cpufreq: Reformat printk() statements
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH v2] cpufreq: Reformat printk() statements
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [PATCH v2] cpufreq: Reformat printk() statements
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [PATCH v2] cpufreq: Reformat printk() statements
- From: Joe Perches <joe@xxxxxxxxxxx>
- Re: [PATCH v2] cpufreq: Reformat printk() statements
- From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
- Re: [PATCH v2] cpufreq: Reformat printk() statements
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- [PATCH v2] cpufreq: Reformat printk() statements
- From: Soren Brinkmann <soren.brinkmann@xxxxxxxxxx>
- Re: [PATCH] cpufreq: enable ARM drivers on arm64
- From: Mark Brown <broonie@xxxxxxxxxx>
- Re: [PATCH] cpufreq: SPEAr: Instantiate as platform_driver
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: enable ARM drivers on arm64
- From: Sudeep Holla <sudeep.holla@xxxxxxx>
- Re: [PATCH] cpufreq: SPEAr: Instantiate as platform_driver
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [Bug 58001] "ondemand" CPU governor never raises frequency (Dell XPS 12)
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 58001] "ondemand" CPU governor never raises frequency (Dell XPS 12)
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 71841] New: ignore_nice_load ignores real load
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH] cpufreq: SPEAr: Instantiate as platform_driver
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- [PATCH v3 37/52] acpi-cpufreq: Fix CPU hotplug callback registration
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [RFC PATCH 3/6] PM / Voltagedomain: introduce voltage domain driver support
- From: Nishanth Menon <nm@xxxxxx>
- Re: [RFC PATCH 3/6] PM / Voltagedomain: introduce voltage domain driver support
- From: Mark Brown <broonie@xxxxxxxxxx>
- Re: [RFC PATCH 3/6] PM / Voltagedomain: introduce voltage domain driver support
- From: Nishanth Menon <nm@xxxxxx>
- Re: [RFC PATCH 3/6] PM / Voltagedomain: introduce voltage domain driver support
- From: Mark Brown <broonie@xxxxxxxxxx>
- Re: [RFC PATCH 3/6] PM / Voltagedomain: introduce voltage domain driver support
- From: Nishanth Menon <nm@xxxxxx>
- Re: [PATCH] cpufreq: Reformat printk() statement
- From: Joe Perches <joe@xxxxxxxxxxx>
- Re: [PATCH] cpufreq: Reformat printk() statement
- From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: Patrik Lundquist <patrik.lundquist@xxxxxxxxx>
- [PATCH] cpufreq: SPEAr: Instantiate as platform_driver
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V1 Resend 0/3] CPUFreq: Minor cleanups for 3.15
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V1 Resend 1/3] cpufreq: add 'freq_table' in struct cpufreq_policy
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V1 Resend 3/3] cpufreq: Remove unnecessary variable/parameter 'frozen'
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V1 Resend 2/3] cpufreq: Remove cpufreq_generic_exit()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/2] cpufreq: Return error if ->get() failed in cpufreq_update_policy()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: use cpufreq_cpu_get to avoid cpufreq_get race conditions
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: Reformat printk() statement
- From: Joe Perches <joe@xxxxxxxxxxx>
- Re: [PATCH] cpufreq: Reformat printk() statement
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: Reformat printk() statement
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- v3.13.5 intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
- From: Patrik Lundquist <patrik.lundquist@xxxxxxxxx>
- Re: [PATCH V6 Resend 1/5] cpufreq: suspend governors on system suspend/hibernate
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- [PATCH] cpufreq: Reformat printk() statement
- From: Soren Brinkmann <soren.brinkmann@xxxxxxxxxx>
- Re: [PATCH V2 3/3] cpufreq: initialize governor for a new policy under policy->rwsem
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: use cpufreq_cpu_get to avoid cpufreq_get race conditions
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH V2 3/3] cpufreq: initialize governor for a new policy under policy->rwsem
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: use cpufreq_cpu_get to avoid cpufreq_get race conditions
- From: Aaron Plattner <aplattner@xxxxxxxxxx>
- Re: [PATCH V2 3/3] cpufreq: initialize governor for a new policy under policy->rwsem
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH V2 3/3] cpufreq: initialize governor for a new policy under policy->rwsem
- From: Saravana Kannan <skannan@xxxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: use cpufreq_cpu_get to avoid cpufreq_get race conditions
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH V2 3/3] cpufreq: initialize governor for a new policy under policy->rwsem
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH V2 3/3] cpufreq: initialize governor for a new policy under policy->rwsem
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH V6 Resend 1/5] cpufreq: suspend governors on system suspend/hibernate
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V6 Resend 1/5] cpufreq: suspend governors on system suspend/hibernate
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- [PATCH] cpufreq: use cpufreq_cpu_get to avoid cpufreq_get race conditions
- From: Aaron Plattner <aplattner@xxxxxxxxxx>
- [RFC v3 2/5] cpufreq:LAB:cpufreq_governor Adjust cpufreq_governor.[h|c] to support LAB
- From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
- [RFC v3 1/5] cpufreq:LAB:ondemand Adjust ondemand to be able to reuse its methods
- From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
- [RFC v3 3/5] cpufreq:LAB:lab Add LAB governor code
- From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
- [RFC v3 5/5] cpufreq:LAB:dts:trats2: Add DTS nodes for LAB governor
- From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
- [RFC v3 4/5] cpufreq:LAB:Kconfig Add LAB definitions to Kconfig
- From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
- [RFC v3 0/5] cpufreq:LAB: Support for LAB governor.
- From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
- [PATCH V2 1/3] cpufreq: move call to __find_governor() to cpufreq_init_policy()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V2 2/3] cpufreq: Initialize policy before making it available for others to use
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V2 3/3] cpufreq: initialize governor for a new policy under policy->rwsem
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/3] cpufreq: move call to __find_governor() to cpufreq_init_policy()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V6 Resend 2/5] cpufreq: Implement cpufreq_generic_suspend()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V6 Resend 3/5] cpufreq: exynos: Use cpufreq_generic_suspend()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V6 Resend 4/5] cpufreq: s5pv210: Use cpufreq_generic_suspend()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V6 Resend 5/5] cpufreq: Tegra: Use cpufreq_generic_suspend()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V6 Resend 1/5] cpufreq: suspend governors on system suspend/hibernate
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v2] drivers: cpufreq: Mark function as static in cpufreq.c
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [RFC PATCH 3/6] PM / Voltagedomain: introduce voltage domain driver support
- From: Mark Brown <broonie@xxxxxxxxxx>
- Re: [PATCH v2] drivers: cpufreq: Mark function as static in cpufreq.c
- From: Patrick Palka <patrick@xxxxxxxxxxxx>
- Re: [PATCH v2] drivers: cpufreq: Mark function as static in cpufreq.c
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: enable ARM drivers on arm64
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH V6 3/7] cpufreq: call driver's suspend/resume for each policy
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH V6 2/7] cpufreq: suspend governors from dpm_{suspend|resume}()
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH 2/3] cpufreq: Initialize policy before making it available for others to use
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH 1/3] cpufreq: move call to __find_governor() to cpufreq_init_policy()
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH 1/3] cpufreq: move call to __find_governor() to cpufreq_init_policy()
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH v3 1/3] cpufreq: stats: Remove redundant cpufreq_cpu_get() call
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH v3 1/3] cpufreq: stats: Remove redundant cpufreq_cpu_get() call
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH v3 3/3] cpufreq: stats: Refactor common code into __cpufreq_stats_create_table()
- From: Saravana Kannan <skannan@xxxxxxxxxxxxxx>
- [PATCH v3 2/3] cpufreq: stats: Fix error handling in __cpufreq_stats_create_table()
- From: Saravana Kannan <skannan@xxxxxxxxxxxxxx>
- [PATCH v3 1/3] cpufreq: stats: Remove redundant cpufreq_cpu_get() call
- From: Saravana Kannan <skannan@xxxxxxxxxxxxxx>
- Re: [RFC PATCH 1/6] PM / Voltagedomain: Add generic clk notifier handler for regulator based dynamic voltage scaling
- From: Felipe Balbi <balbi@xxxxxx>
- Re: [RFC PATCH 1/6] PM / Voltagedomain: Add generic clk notifier handler for regulator based dynamic voltage scaling
- From: Nishanth Menon <nm@xxxxxx>
- Re: [PATCH 3/3] cpufreq: stats: Refactor common code into __cpufreq_stats_create_table()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v2] drivers: cpufreq: Mark function as static in cpufreq.c
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [RFC PATCH 1/6] PM / Voltagedomain: Add generic clk notifier handler for regulator based dynamic voltage scaling
- From: Mike Turquette <mturquette@xxxxxxxxxx>
- Re: [RFC PATCH 1/6] PM / Voltagedomain: Add generic clk notifier handler for regulator based dynamic voltage scaling
- From: Nishanth Menon <nm@xxxxxx>
- Re: [PATCH v3] drivers: cpufreq: Mark function as static in cpufreq.c
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [PATCH v3] drivers: cpufreq: Mark function as static in cpufreq.c
- From: josh@xxxxxxxxxxxxxxxx
- Re: [PATCH v3] drivers: cpufreq: Mark function as static in cpufreq.c
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- [PATCH 2/3] cpufreq: stats: Fix error handling in __cpufreq_stats_create_table()
- From: Saravana Kannan <skannan@xxxxxxxxxxxxxx>
- [PATCH 3/3] cpufreq: stats: Refactor common code into __cpufreq_stats_create_table()
- From: Saravana Kannan <skannan@xxxxxxxxxxxxxx>
- [PATCH 1/3] cpufreq: stats: Remove redundant cpufreq_cpu_get() call
- From: Saravana Kannan <skannan@xxxxxxxxxxxxxx>
- Re: [PATCH v2] drivers: cpufreq: Mark function as static in cpufreq.c
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: [PATCH v2] drivers: cpufreq: Mark function as static in cpufreq.c
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [PATCH v2] drivers: cpufreq: Mark function as static in cpufreq.c
- From: Rashika Kheria <rashika.kheria@xxxxxxxxx>
- [PATCH v3] drivers: cpufreq: Mark function as static in cpufreq.c
- From: Rashika Kheria <rashika.kheria@xxxxxxxxx>
- Re: [PATCH v2] drivers: cpufreq: Mark function as static in cpufreq.c
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- [PATCH v2] drivers: cpufreq: Mark function as static in cpufreq.c
- From: Rashika Kheria <rashika.kheria@xxxxxxxxx>
- Re: [PATCH] drivers: cpufreq: Remove unused function in cpufreq.c
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- [PATCH] drivers: cpufreq: Remove unused function in cpufreq.c
- From: Rashika Kheria <rashika.kheria@xxxxxxxxx>
- Re: [PATCH 1/2] cpufreq: Return error if ->get() failed in cpufreq_update_policy()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/2] cpufreq: Return error if ->get() failed in cpufreq_update_policy()
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- Re: [RFC PATCH 1/6] PM / Voltagedomain: Add generic clk notifier handler for regulator based dynamic voltage scaling
- From: Nishanth Menon <nm@xxxxxx>
- Re: [PATCH 1/2] cpufreq: Return error if ->get() failed in cpufreq_update_policy()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/2] cpufreq: Return error if ->get() failed in cpufreq_update_policy()
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
- [PATCH V2] cpufreq: Return error if ->get() failed in cpufreq_update_policy()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 2/3] cpufreq: Initialize policy before making it available for others to use
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 3/3] cpufreq: initialize governor for a new policy under policy->rwsem
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 1/3] cpufreq: move call to __find_governor() to cpufreq_init_policy()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/2] cpufreq: Return error if ->get() failed in cpufreq_update_policy()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/2] cpufreq: Return error if ->get() failed in cpufreq_update_policy()
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [RFC PATCH 1/6] PM / Voltagedomain: Add generic clk notifier handler for regulator based dynamic voltage scaling
- From: Mike Turquette <mturquette@xxxxxxxxxx>
- Re: [PATCH 1/2] cpufreq: Return error if ->get() failed in cpufreq_update_policy()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: Commit fcb6a15c2e7e (intel_pstate: Take core C0 time into account for core busy calculation) sucks rocks
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: Commit fcb6a15c2e7e (intel_pstate: Take core C0 time into account for core busy calculation) sucks rocks
- From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH V5 0/7] cpufreq: suspend early/resume late: dpm_{suspend|resume}()
- From: Stephen Warren <swarren@xxxxxxxxxxxxx>
- Re: [RFC PATCH 3/6] PM / Voltagedomain: introduce voltage domain driver support
- From: Nishanth Menon <nm@xxxxxx>
- [Bug 70941] 'powersave' performance excessively slow on Dell Venue 8 Pro (Baytrail tablet)
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH V6 0/7] cpufreq: suspend early/resume late: dpm_{suspend|resume}()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V5 0/7] cpufreq: suspend early/resume late: dpm_{suspend|resume}()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [RFC PATCH 3/6] PM / Voltagedomain: introduce voltage domain driver support
- From: Mark Brown <broonie@xxxxxxxxxx>
- [PATCH] cpufreq: enable ARM drivers on arm64
- From: Mark Brown <broonie@xxxxxxxxxx>
- [Bug 65671] hibernation - IO errors writing to swap, crashing apps, 3,11.8 worked
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 70941] 'powersave' performance excessively slow on Dell Venue 8 Pro (Baytrail tablet)
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 70941] New: 'powersave' performance excessively slow on Dell Venue 8 Pro (Baytrail tablet)
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [3.14-rc3] possible regression Haswell runs only at 770Mhz with powersave governor
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [3.14-rc3] possible regression Haswell runs only at 770Mhz with powersave governor
- From: Otto Meier <gf435@xxxxxxx>
- Re: Commit fcb6a15c2e7e (intel_pstate: Take core C0 time into account for core busy calculation) sucks rocks
- From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH V5 0/7] cpufreq: suspend early/resume late: dpm_{suspend|resume}()
- From: Stephen Warren <swarren@xxxxxxxxxxxxx>
- Re: [3.14-rc3] possible regression Haswell runs only at 770Mhz with powersave governor
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
[Index of Archives]
[Linux Kernel Devel]
[Linux USB Devel]
[Linux SCSI]
[Samba]
[Yosemite News]