Linux CPU Freq

• Thread Index

• RFC: sunsetting the cpufreq list
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• cpufreq-info SIGKILL or freeze unkillable in read(.../cpu0/cpufreq/stats/time_in_state)
  • From: Jonas Bechtel <post@xxxxxxxxxxx>
• Fwd: Intel_pstate locked lowest mhz
  • From: Terry M <zecatfish@xxxxxxxxx>
• Re: can not seem to set cpufreq to max performance with newer kernels for xeons X56xx
  • From: Jelle de Jong <jelledejong@xxxxxxxxxxxxx>
• can not seem to set cpufreq to max performance with newer kernels for xeons X56xx
  • From: Jelle de Jong <jelledejong@xxxxxxxxxxxxx>
• can not seem to set cpufreq to max performance with newer kernels
  • From: Jelle de Jong <jelledejong@xxxxxxxxxxxxx>
• Setting minimal cpu fequencies
  • From: Bernard KORSEC <bernard.korsec@xxxxxxxxx>
• bug userspace
  • From: Mister Goo <goobubble@xxxxxxxxx>
• scaling governor kernel 4.14.40 vs 4.17.rc
  • From: abhishek koundal <akoundal@xxxxxxxxx>
• Unexpected outcome using cpufreq-set on Xeon Platinum CPU
  • From: Jeffrey Lane <jeffrey.lane@xxxxxxxxxxxxx>
• current policy: frequency should be within 1.50 GHz and 1.50 GHz.
  • From: Klaudio Zic <vnn2017@xxxxxxxxx>
• cpufreq debian 9, intel i7 908x
  • From: Micha W <cellmw@xxxxxxxxx>
• Re: [PATCH 07/34] cpufreq: cris: remove calls to cpufreq_notify_transition()
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [PATCH 07/34] cpufreq: cris: remove calls to cpufreq_notify_transition()
  • From: Jesper Nilsson <jesper.nilsson@xxxxxxxx>
• CPU frequency governor problem
  • From: Edward Statham <edward.statham@xxxxxxxxx>
• Godaveri
  • From: <jan.weber@xxxxxxxx>
• [PATCH] cpufrequtils: Report offline cpus in cpufreq-info
  • From: Akshay Adiga <akshay.adiga@xxxxxxxxxxxxxxxxxx>
• Re: [GIT PULL] Integrator DTS and defconfig changes
  • From: Linus Walleij <linus.walleij@xxxxxxxxxx>
• Re: [GIT PULL] Integrator DTS and defconfig changes
  • From: Olof Johansson <olof@xxxxxxxxx>
• Re: [GIT PULL] Integrator DTS and defconfig changes
  • From: Linus Walleij <linus.walleij@xxxxxxxxxx>
• Re: [GIT PULL] Integrator DTS and defconfig changes
  • From: Olof Johansson <olof@xxxxxxxxx>
• [GIT PULL] Integrator DTS and defconfig changes
  • From: Linus Walleij <linus.walleij@xxxxxxxxxx>
• [Bug 101241] cpufreq ondemand does not work on AMD GX-416RA SOC
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 101241] cpufreq ondemand does not work on AMD GX-416RA SOC
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• amd9590
  • From: Richard Jasmin <richardjasmin123@xxxxxxxxxxx>
• Re: [PATCH] cpufreq: Add Broadcom BCM2835 CPU frequency control driver
  • From: Eric Anholt <eric@xxxxxxxxxx>
• hotplug governor
  • From: Sriram V <vshrirama@xxxxxxxxx>
• [Bug 71841] cpufreq ondemand ignore_nice_load doesn't work
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 71841] cpufreq ondemand ignore_nice_load doesn't work
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 71841] cpufreq ondemand ignore_nice_load doesn't work
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 65501] Blind angle of 1% between up_threshold and down_threshold
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 65501] Blind angle of 1% between up_threshold and down_threshold
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 65501] Blind angle of 1% between up_threshold and down_threshold
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 100771] When activating ignore_nice_load with governor ondemand performance drops for normal processes.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 100771] When activating ignore_nice_load with governor ondemand performance drops for normal processes.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 100771] When activating ignore_nice_load with governor ondemand performance drops for normal processes.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 71841] cpufreq ondemand ignore_nice_load doesn't work
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 71841] cpufreq ondemand ignore_nice_load doesn't work
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 100771] When activating ignore_nice_load with governor ondemand performance drops for normal processes.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 100771] When activating ignore_nice_load with governor ondemand performance drops for normal processes.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 100771] When activating ignore_nice_load with governor ondemand performance drops for normal processes.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 69821] setting CONFIG_HZ_PERIODIC locks cpu at the lowest frequency using ONDEMAND
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 69821] setting CONFIG_HZ_PERIODIC locks cpu at the lowest frequency using ONDEMAND
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 69821] setting CONFIG_HZ_PERIODIC locks cpu at the lowest frequency using ONDEMAND
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 69821] setting CONFIG_HZ_PERIODIC locks cpu at the lowest frequency using ONDEMAND
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 101241] cpufreq ondemand does not work on AMD GX-416RA SOC
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: Changing CPU frequency in atomic (schedule / scheduler_tick)
  • From: Punit Agrawal <punit.agrawal@xxxxxxx>
• Help
  • From: Don Malachia <don.malachia@xxxxxxxxx>
• Re: issues on driver CPU
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• issues on driver CPU
  • From: Lorenzo Scattolin <lorenzo.scattolin04@xxxxxxxxx>
• [Bug 101241] cpufreq ondemand not work in my system
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 101241] cpufreq ondemand not work in my system
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 65501] Blind angle of 1% between up_threshold and down_threshold
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [PATCH v6 2/2] cpufreq: intel_pstate: Fix the FSB feq for Airmont
  • From: plongepe <philippe.longepe@xxxxxxxxxxxxxxx>
• [PATCH v2 1/2] cpufreq: intel_pstate: Replace BYT by ATOM
  • From: plongepe <philippe.longepe@xxxxxxxxxxxxxxx>
• Re: [PATCH] cpufreq: Add Broadcom BCM2835 CPU frequency control driver
  • From: Stephen Warren <swarren@xxxxxxxxxxxxx>
• [PATCH] cpufreq: Add Broadcom BCM2835 CPU frequency control driver
  • From: Lubomir Rintel <lkundrak@xxxxx>
• Proposition D'Affaires:
  • From: Mong-Hoi@xxxxxxxxxxxxxxx
• RE: cpufreq doesn't work quite on Dell GX520 with Pentium D at 2.80gHz
  • From: "Doug Smythies" <dsmythies@xxxxxxxxx>
• cpufreq doesn't work quite on Dell GX520 with Pentium D at 2.80gHz
  • From: Deirdre Kylie <kylie.deirdre@xxxxxxxxx>
• Re: about system time incorrect after changing cpu frequency
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: about system time incorrect after changing cpu frequency
  • From: vichy <vichy.kuo@xxxxxxxxx>
• Re: about system time incorrect after changing cpu frequency
  • From: vichy <vichy.kuo@xxxxxxxxx>
• Re: about system time incorrect after changing cpu frequency
  • From: Jisheng Zhang <jszhang@xxxxxxxxxxx>
• Re: about system time incorrect after changing cpu frequency
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: about system time incorrect after changing cpu frequency
  • From: vichy <vichy.kuo@xxxxxxxxx>
• Re: about system time incorrect after changing cpu frequency
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• about system time incorrect after changing cpu frequency
  • From: vichy <vichy.kuo@xxxxxxxxx>
• Re: some question about cpubench
  • From: vichy <vichy.kuo@xxxxxxxxx>
• Re: Changing CPU frequency in atomic (schedule / scheduler_tick)
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: Changing CPU frequency in atomic (schedule / scheduler_tick)
  • From: Guru Prasad <gurupras@xxxxxxxxxxx>
• Re: Changing CPU frequency in atomic (schedule / scheduler_tick)
  • From: Guru Prasad <gurupras@xxxxxxxxxxx>
• Re: Changing CPU frequency in atomic (schedule / scheduler_tick)
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Changing CPU frequency in atomic (schedule / scheduler_tick)
  • From: Guru Prasad <gurupras@xxxxxxxxxxx>
• Re: Using a temperature sensor with 1-bit output for CPU throttling
  • From: Mason <slash.tmp@xxxxxxx>
• Re: Using a temperature sensor with 1-bit output for CPU throttling
  • From: Mason <slash.tmp@xxxxxxx>
• [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: Using a temperature sensor with 1-bit output for CPU throttling
  • From: Mason <slash.tmp@xxxxxxx>
• Re: Using a temperature sensor with 1-bit output for CPU throttling
  • From: Mason <slash.tmp@xxxxxxx>
• [Bug 101241] New: cpufreq ondemand not work in my system
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 100771] When activating ignore_nice_load with governor ondemand performance drops for normal processes.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Clock speed Display bug when underclocked.
  • From: James Phillips <kernel.org@xxxxxxxxxxxxx>
• Re: [PATCH] cpufreq: qoriq: optimize the CPU frequency switching time
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• [PATCH] cpufreq: qoriq: optimize the CPU frequency switching time
  • From: <Yuantian.Tang@xxxxxxxxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Mason <slash.tmp@xxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Mason <slash.tmp@xxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Mason <slash.tmp@xxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Mason <slash.tmp@xxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Mason <slash.tmp@xxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Mason <slash.tmp@xxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Mason <slash.tmp@xxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Mason <slash.tmp@xxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Mason <slash.tmp@xxxxxxx>
• Re: Using a temperature sensor with 1-bit output for CPU throttling
  • From: Punit Agrawal <punit.agrawal@xxxxxxx>
• Re: Using a temperature sensor with 1-bit output for CPU throttling
  • From: Mason <slash.tmp@xxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Mason <slash.tmp@xxxxxxx>
• Re: Using a temperature sensor with 1-bit output for CPU throttling
  • From: Mason <slash.tmp@xxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Mason <slash.tmp@xxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Mason <slash.tmp@xxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Mason <slash.tmp@xxxxxxx>
• Re: schedule_timeout sleeps too long after dividing CPU frequency
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• schedule_timeout sleeps too long after dividing CPU frequency
  • From: Mason <slash.tmp@xxxxxxx>
• Re: Using a temperature sensor with 1-bit output for CPU throttling
  • From: Mason <slash.tmp@xxxxxxx>
• Using a temperature sensor with 1-bit output for CPU throttling
  • From: Mason <slash.tmp@xxxxxxx>
• [Bug 91141] acpi-cpufreq cannot be loaded.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU - AMD Athlon(tm) 5150 APU with Radeon(tm) R3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU - AMD Athlon(tm) 5150 APU with Radeon(tm) R3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re:do not need a prescription
  • From: "Ryan" <order@xxxxxxxxxxxx>
• [Bug 60587] Only two p-states visible on AMD FX-8350
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: cpufreq-info and acpi-cpufreq: reporting MSR_IA32_PERF_CTL as "actual frequency"
  • From: Len Brown <lenb@xxxxxxxxxx>
• [Bug 91141] acpi-cpufreq cannot be loaded.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Stephen Boyd <sboyd@xxxxxxxxxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Stephen Boyd <sboyd@xxxxxxxxxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Stephen Boyd <sboyd@xxxxxxxxxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Stephen Boyd <sboyd@xxxxxxxxxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Michal Simek <michal.simek@xxxxxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Stefan Agner <stefan@xxxxxxxx>
• Re: cpuidle vs suspend vs something else
  • From: Pavel Machek <pavel@xxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Stefan Agner <stefan@xxxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: cpuidle vs suspend vs something else
  • From: Mike Turquette <mturquette@xxxxxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: cpuidle vs suspend vs something else
  • From: Krzysztof Kozlowski <k.kozlowski@xxxxxxxxxxx>
• cpuidle vs suspend vs something else
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: RFC on cpufreq implementation
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: RFC on cpufreq implementation
  • From: Måns Rullgård <mans@xxxxxxxxx>
• Re: RFC on cpufreq implementation
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: RFC on cpufreq implementation
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: RFC on cpufreq implementation
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: RFC on cpufreq implementation
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: RFC on cpufreq implementation
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: Delays, clocks, timers, hrtimers, etc
  • From: Mason <mpeg.blue@xxxxxxx>
• Delays, clocks, timers, hrtimers, etc
  • From: Mason <mpeg.blue@xxxxxxx>
• linux-next: tidy up of trees
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [Bug 91141] acpi-cpufreq cannot be loaded.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: RFC on cpufreq implementation
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: RFC on cpufreq implementation
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: RFC on cpufreq implementation
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: RFC on cpufreq implementation
  • From: Amit Kucheria <amit.kucheria@xxxxxxxxxxxxx>
• Re: RFC on cpufreq implementation
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: RFC on cpufreq implementation
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: RFC on cpufreq implementation
  • From: Javi Merino <javi.merino@xxxxxxx>
• Re: RFC on cpufreq implementation
  • From: Krzysztof Kozlowski <k.kozlowski@xxxxxxxxxxx>
• Re: RFC on cpufreq implementation
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: RFC on cpufreq implementation
  • From: Krzysztof Kozlowski <k.kozlowski@xxxxxxxxxxx>
• RFC on cpufreq implementation
  • From: Mason <mpeg.blue@xxxxxxx>
• [Bug 91141] acpi-cpufreq cannot be loaded.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 91141] acpi-cpufreq cannot be loaded.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 91141] acpi-cpufreq cannot be loaded.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 91141] acpi-cpufreq cannot be loaded.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 91141] acpi-cpufreq cannot be loaded.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 91141] acpi-cpufreq cannot be loaded.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 91141] acpi-cpufreq cannot be loaded.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH] input: CPU frequency booster
  • From: Pavel Machek <pavel@xxxxxx>
• [Bug 91141] acpi-cpufreq cannot be loaded.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 91141] acpi-cpufreq cannot be loaded.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 91141] New: acpi-cpufreq cannot be loaded.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: cpufreq-info and acpi-cpufreq: reporting MSR_IA32_PERF_CTL as "actual frequency"
  • From: Magdalena Dobosz <maj.dobosz@xxxxxxxxx>
• Re: cpufreq-info and acpi-cpufreq: reporting MSR_IA32_PERF_CTL as "actual frequency"
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: cpufreq-info and acpi-cpufreq: reporting MSR_IA32_PERF_CTL as "actual frequency"
  • From: Magdalena Dobosz <maj.dobosz@xxxxxxxxx>
• Re: cpufreq-info and acpi-cpufreq: reporting MSR_IA32_PERF_CTL as "actual frequency"
  • From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
• Re: cpufreq-info and acpi-cpufreq: reporting MSR_IA32_PERF_CTL as "actual frequency"
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: How many frequencies would cpufreq optimally like to manage?
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: How many frequencies would cpufreq optimally like to manage?
  • From: Mason <mpeg.blue@xxxxxxx>
• cpufreq-info and acpi-cpufreq: reporting MSR_IA32_PERF_CTL as "actual frequency"
  • From: Magdalena Dobosz <maj.dobosz@xxxxxxxxx>
• Re: How many frequencies would cpufreq optimally like to manage?
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: How many frequencies would cpufreq optimally like to manage?
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: Race condition in cpufreq
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: How many frequencies would cpufreq optimally like to manage?
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: How many frequencies would cpufreq optimally like to manage?
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: How many frequencies would cpufreq optimally like to manage?
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• How many frequencies would cpufreq optimally like to manage?
  • From: Mason <mpeg.blue@xxxxxxx>
• Race condition in cpufreq
  • From: Arun KS <arunks.linux@xxxxxxxxx>
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU - AMD Athlon(tm) 5150 APU with Radeon(tm) R3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 83701] divide error 0000 in intel_pstate_set_pstate
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 62551] AMD Phenom II 955.: The system freezes for a moment when the CPU scaling is enabled
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 86461] intel_pstate does not obey min/max frequencies set by user
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU - AMD Athlon(tm) 5150 APU with Radeon(tm) R3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 71841] cpufreq ondemand ignore_nice_load doesn't work
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 86461] intel_pstate does not obey min/max frequencies set by user
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 58001] "ondemand" CPU governor never raises frequency (Dell XPS 12)
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 86461] intel_pstate does not obey min/max frequencies set by user
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 86461] intel_pstate does not obey min/max frequencies set by user
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 86461] intel_pstate does not obey min/max frequencies set by user
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 86461] intel_pstate does not obey min/max frequencies set by user
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 86461] intel_pstate does not obey min/max frequencies set by user
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 86461] New: intel_pstate does not obey min/max frequencies set by user
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [cpufreq] 48ed83b84da: scaling_governor write error
  • From: Fengguang Wu <fengguang.wu@xxxxxxxxx>
• Re: Potential cpufreq backports for v3.10 LTS
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: Potential cpufreq backports for v3.10 LTS
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Potential cpufreq backports for v3.10 LTS
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: Potential cpufreq backports for v3.10 LTS
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Potential cpufreq backports for v3.10 LTS
  • From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
• Re: Potential cpufreq backports for v3.10 LTS
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: Potential cpufreq backports for v3.10 LTS
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Potential cpufreq backports for v3.10 LTS
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: Potential cpufreq backports for v3.10 LTS
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Potential cpufreq backports for v3.10 LTS
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Potential cpufreq backports for v3.10 LTS
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: cpufreq dir under /sys/devices/system/cpu/cpu* is not present for online=0 cpus
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: ARM: mx28: cpufreq-cpu0 support?
  • From: Stefan Wahren <info@xxxxxxxxxxxxxx>
• [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 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 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
• Re: ARM: mx28: cpufreq-cpu0 support?
  • From: Fabio Estevam <festevam@xxxxxxxxx>
• Re: ARM: mx28: cpufreq-cpu0 support?
  • From: Stefan Wahren <info@xxxxxxxxxxxxxx>
• cpufreq dir under /sys/devices/system/cpu/cpu* is not present for online=0 cpus
  • From: Ragu <raguramanmm@xxxxxxxxx>
• Re: ARM: mx28: cpufreq-cpu0 support?
  • From: Fabio Estevam <festevam@xxxxxxxxx>
• Re: ARM: mx28: cpufreq-cpu0 support?
  • From: Stefan Wahren <info@xxxxxxxxxxxxxx>
• [Bug 58001] "ondemand" CPU governor never raises frequency (Dell XPS 12)
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 56071] Ondemand doesn't set correct low frequency
  • 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 84851] CPU scaled down to 600 MHz even under load
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 84851] New: CPU scaled down to 600 MHz even under load
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• cpufreq values displayed 20% high on Intel J1900 BayTrail CPU
  • From: Grant Coady <gcoady.lk@xxxxxxxxx>
• [Bug 65671] Asus A8V deluxe(AMD): hibernation - IO errors writing to swap, crashing apps, 3,11.8 worked, unless rmmod powernow_k8
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 71841] AMD64:ignore_nice_load ignores real load
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 83701] divide error 0000 in intel_pstate_set_pstate
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: ARM: mx28: cpufreq-cpu0 support?
  • From: Fabio Estevam <festevam@xxxxxxxxx>
• Re: cpufreq-info
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: ARM: mx28: cpufreq-cpu0 support?
  • From: Stefan Wahren <info@xxxxxxxxxxxxxx>
• [Bug 83701] New: divide error 0000 in intel_pstate_set_pstate
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• cpufreq-info
  • From: Jean Oberson <jo@xxxxxxxxxxxxxxx>
• Re: ARM: mx28: cpufreq-cpu0 support?
  • From: Fabio Estevam <festevam@xxxxxxxxx>
• Re: ARM: mx28: cpufreq-cpu0 support?
  • From: Stefan Wahren <info@xxxxxxxxxxxxxx>
• Re: ARM: mx28: cpufreq-cpu0 support?
  • From: Fabio Estevam <festevam@xxxxxxxxx>
• Re: ARM: mx28: cpufreq-cpu0 support?
  • From: Fabio Estevam <festevam@xxxxxxxxx>
• [Bug 83151] Intel Turbo can't be disabled/enabled under certain condictions
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 83151] Intel Turbo can't be disabled/enabled under certain condictions
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 83151] Intel Turbo can't be disabled/enabled under certain condictions
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: ARM: mx28: cpufreq-cpu0 support?
  • From: Stefan Wahren <info@xxxxxxxxxxxxxx>
• Re: ARM: mx28: cpufreq-cpu0 support?
  • From: Shawn Guo <shawn.guo@xxxxxxxxxx>
• [Bug 83151] New: Intel Turbo can't be disabled/enabled under certain condictions
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• ARM: mx28: cpufreq-cpu0 support?
  • From: Stefan Wahren <info@xxxxxxxxxxxxxx>
• [Bug 72361] AMD APU reset infinite
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [RFC 0/3] Experimental patchset for CPPC
  • From: Ashwin Chaugule <ashwin.chaugule@xxxxxxxxxx>
• Re: [RFC 0/3] Experimental patchset for CPPC
  • From: Ashwin Chaugule <ashwin.chaugule@xxxxxxxxxx>
• Re: [RFC 0/3] Experimental patchset for CPPC
  • From: Len Brown <lenb@xxxxxxxxxx>
• Re: [RFC 0/3] Experimental patchset for CPPC
  • From: Len Brown <lenb@xxxxxxxxxx>
• Re: [RFC 0/3] Experimental patchset for CPPC
  • From: Ashwin Chaugule <ashwin.chaugule@xxxxxxxxxx>
• Re: [RFC 0/3] Experimental patchset for CPPC
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [RFC 0/3] Experimental patchset for CPPC
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [RFC 0/3] Experimental patchset for CPPC
  • From: Ashwin Chaugule <ashwin.chaugule@xxxxxxxxxx>
• Re: [RFC 0/3] Experimental patchset for CPPC
  • From: Ashwin Chaugule <ashwin.chaugule@xxxxxxxxxx>
• Re: [RFC 0/3] Experimental patchset for CPPC
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [RFC 0/3] Experimental patchset for CPPC
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [RFC 0/3] Experimental patchset for CPPC
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [RFC 0/3] Experimental patchset for CPPC
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [RFC 0/3] Experimental patchset for CPPC
  • From: Ashwin Chaugule <ashwin.chaugule@xxxxxxxxxx>
• Re: [RFC 0/3] Experimental patchset for CPPC
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [RFC 0/3] Experimental patchset for CPPC
  • From: Ashwin Chaugule <ashwin.chaugule@xxxxxxxxxx>
• Re: [RFC 0/3] Experimental patchset for CPPC
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [RFC 3/3] CPPC: Add ACPI accessors to CPC registers
  • From: Ashwin Chaugule <ashwin.chaugule@xxxxxxxxxx>
• Re: [RFC 2/3] CPPC: Add support for Collaborative Processor Performance Control
  • From: Ashwin Chaugule <ashwin.chaugule@xxxxxxxxxx>
• Re: [RFC 1/3] ACPI: Add support for Platform Communication Channel
  • From: Ashwin Chaugule <ashwin.chaugule@xxxxxxxxxx>
• Re: [RFC 0/3] Experimental patchset for CPPC
  • From: Ashwin Chaugule <ashwin.chaugule@xxxxxxxxxx>
• [RFC 1/3] ACPI: Add support for Platform Communication Channel
  • From: Ashwin Chaugule <ashwin.chaugule@xxxxxxxxxx>
• [RFC 3/3] CPPC: Add ACPI accessors to CPC registers
  • From: Ashwin Chaugule <ashwin.chaugule@xxxxxxxxxx>
• [RFC 2/3] CPPC: Add support for Collaborative Processor Performance Control
  • From: Ashwin Chaugule <ashwin.chaugule@xxxxxxxxxx>
• [RFC 0/3] Experimental patchset for CPPC
  • From: Ashwin Chaugule <ashwin.chaugule@xxxxxxxxxx>
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 62551] AMD Phenom II 955.: The system freezes for a moment when the CPU scaling is enabled
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 75661] AMD A8-4500M: acpi-cpufreq cannot use lowest reported P-state
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 62551] AMD Phenom II 955.: The system freezes for a moment when the CPU scaling is enabled
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH v2] cpufreq: tests: Providing cpufreq regression test
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• [Bug 81131] Not found this subsystem directory /sys/devices/system/cpu/cpufreq
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81701] New: OOPS in cpufreq driver with AMD Kaveri CPU
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 75661] AMD A8-4500M: acpi-cpufreq cannot use lowest reported P-state
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 71841] AMD64:ignore_nice_load ignores real load
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 65671] Asus A8V deluxe(AMD): hibernation - IO errors writing to swap, crashing apps, 3,11.8 worked, unless rmmod powernow_k8
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81131] Not found this subsystem directory /sys/devices/system/cpu/cpufreq
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81021] AMD CPUs w/ Integrated Graphics (APUs) And Turbo Core Only Boost If "fglrx" Module Is Loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 62551] AMD Phenom II 955.: The system freezes for a moment when the CPU scaling is enabled
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81131] New: Not found this subsystem directory /sys/devices/system/cpu/cpufreq
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 81021] New: AMD CPUs w/ Integrated Graphics (APUs) And Turbo Core Only Boost If "fglrx" Module Is Loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH v2] cpufreq: tests: Providing cpufreq regression test
  • From: "Javi Merino" <javi.merino@xxxxxxx>
• Re: [PATCH v2] cpufreq: tests: Providing cpufreq regression test
  • From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
• Re: [PATCH v2] cpufreq: tests: Providing cpufreq regression test
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [PATCH v2] cpufreq: tests: Providing cpufreq regression test
  • From: Andrew Lunn <andrew@xxxxxxx>
• Re: [PATCH v2] cpufreq: tests: Providing cpufreq regression test
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [PATCH v2] cpufreq: tests: Providing cpufreq regression test
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [PATCH v2] cpufreq: tests: Providing cpufreq regression test
  • From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
• Re: [PATCH v2] cpufreq: tests: Providing cpufreq regression test
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [PATCH v2] cpufreq: tests: Providing cpufreq regression test
  • From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
• Re: [PATCH v2] cpufreq: tests: Providing cpufreq regression test
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [PATCH] cpufreq: tests: Providing cpufreq regression test
  • From: Sachin Kamat <spk.linux@xxxxxxxxx>
• [PATCH v2] cpufreq: tests: Providing cpufreq regression test
  • From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
• [Bug 72361] AMD APU reset infinite
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 80651] [intel_pstate] pstate settings are lost during suspend/resume cycle
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 80651] [intel_pstate] pstate settings are lost during suspend/resume cycle
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 80651] [intel_pstate] pstate settings are lost during suspend/resume cycle
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 80651] [intel_pstate] pstate settings are lost during suspend/resume cycle
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 80651] [intel_pstate] pstate settings are lost during suspend/resume cycle
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 80651] New: [intel_pstate] pstate settings are lost during suspend/resume cycle
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH] cpufreq: tests: Providing cpufreq regression test
  • From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
• Re: [PATCH] cpufreq: tests: Providing cpufreq regression test
  • From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
• Re: [PATCH] cpufreq: tests: Providing cpufreq regression test
  • From: Sachin Kamat <spk.linux@xxxxxxxxx>
• Re: [PATCH] cpufreq: tests: Providing cpufreq regression test
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• [PATCH] cpufreq: tests: Providing cpufreq regression test
  • From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
• [Bug 72361] AMD APU reset infinite
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: RFC: Leave sysfs nodes alone during hotplug
  • From: Saravana Kannan <skannan@xxxxxxxxxxxxxx>
• Re: [PATCH v4 7/8] ARM: Exynos: switch to using generic cpufreq-cpu0 driver
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: RFC: Leave sysfs nodes alone during hotplug
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: RFC: Leave sysfs nodes alone during hotplug
  • From: skannan@xxxxxxxxxxxxxx
• Re: RFC: Leave sysfs nodes alone during hotplug
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: RFC: Leave sysfs nodes alone during hotplug
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: RFC: Leave sysfs nodes alone during hotplug
  • From: Saravana Kannan <skannan@xxxxxxxxxxxxxx>
• Re: RFC: Leave sysfs nodes alone during hotplug
  • From: Todd Poynor <toddpoynor@xxxxxxxxxx>
• Re: RFC: Leave sysfs nodes alone during hotplug
  • From: Saravana Kannan <skannan@xxxxxxxxxxxxxx>
• Re: RFC: Leave sysfs nodes alone during hotplug
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• RFC: Leave sysfs nodes alone during hotplug
  • From: Saravana Kannan <skannan@xxxxxxxxxxxxxx>
• Re: [PATCH 1/4] clk: Introduce 'clk_find_nearest_rate()'
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• Re: [PATCH 1/4] clk: Introduce 'clk_find_nearest_rate()'
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [PATCH 1/4] clk: Introduce 'clk_find_nearest_rate()'
  • From: Boris BREZILLON <boris.brezillon@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/4] clk: Introduce 'clk_find_nearest_rate()'
  • From: Boris BREZILLON <boris.brezillon@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/4] clk: Introduce 'clk_find_nearest_rate()'
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• Re: [PATCH 1/4] clk: Introduce 'clk_find_nearest_rate()'
  • From: Boris BREZILLON <boris.brezillon@xxxxxxxxxxxxxxxxxx>
• [Bug 72361] AMD APU reset infinite
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [PATCH 0/4] Introduce clk_find_nearest_rate()
  • From: Soren Brinkmann <soren.brinkmann@xxxxxxxxxx>
• [PATCH 1/4] clk: Introduce 'clk_find_nearest_rate()'
  • From: Soren Brinkmann <soren.brinkmann@xxxxxxxxxx>
• [PATCH 4/4] ARM: zynq: dt: Use properly rounded frequencies in OPPs
  • From: Soren Brinkmann <soren.brinkmann@xxxxxxxxxx>
• [PATCH 3/4] net: macb: Use clk_find_nearest_rate() API
  • From: Soren Brinkmann <soren.brinkmann@xxxxxxxxxx>
• [PATCH 2/4] cpufreq: cpu0: Use clk_find_nearest_rate()
  • From: Soren Brinkmann <soren.brinkmann@xxxxxxxxxx>
• Re: [PATCH v6 1/6] clk: samsung: add infrastructure to register cpu clocks
  • From: amit daniel kachhap <amit.daniel@xxxxxxxxxxx>
• [Bug 77771] Intel P-State: Constantly changing CPU frequencies on idle system.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH v6 1/6] clk: samsung: add infrastructure to register cpu clocks
  • From: Arjun K V <arjunkv243@xxxxxxxxx>
• Re: [PATCH v6 3/6] clk: exynos: use cpu-clock provider type to represent arm clock
  • From: amit daniel kachhap <amit.daniel@xxxxxxxxxxx>
• Re: [PATCH v6 1/6] clk: samsung: add infrastructure to register cpu clocks
  • From: amit daniel kachhap <amit.daniel@xxxxxxxxxxx>
• [Bug 77771] Intel P-State: Constantly changing CPU frequencies on idle system.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77771] Intel P-State: Constantly changing CPU frequencies on idle system.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77771] Intel P-State: Constantly changing CPU frequencies on idle system.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77771] Intel P-State: Constantly changing CPU frequencies on idle system.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH v6 0/6] cpufreq: use generic cpufreq drivers for exynos platforms
  • From: Thomas Abraham <ta.omasab@xxxxxxxxx>
• Re: [PATCH v6 0/6] cpufreq: use generic cpufreq drivers for exynos platforms
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• [PATCH v6 6/6] cpufreq: exynos: remove exynos4210/5250 specific cpufreq driver support
  • From: Thomas Abraham <thomas.ab@xxxxxxxxxxx>
• [PATCH v6 5/6] ARM: Exynos: switch to using generic cpufreq driver for exynos4210/5250
  • From: Thomas Abraham <thomas.ab@xxxxxxxxxxx>
• [PATCH v6 4/6] ARM: dts: Exynos: add cpu nodes, opp and cpu clock configuration data
  • From: Thomas Abraham <thomas.ab@xxxxxxxxxxx>
• [PATCH v6 3/6] clk: exynos: use cpu-clock provider type to represent arm clock
  • From: Thomas Abraham <thomas.ab@xxxxxxxxxxx>
• [PATCH v6 2/6] clk: samsung: register exynos5420 apll/kpll configuration data
  • From: Thomas Abraham <thomas.ab@xxxxxxxxxxx>
• [PATCH v6 1/6] clk: samsung: add infrastructure to register cpu clocks
  • From: Thomas Abraham <thomas.ab@xxxxxxxxxxx>
• [PATCH v6 0/6] cpufreq: use generic cpufreq drivers for exynos platforms
  • From: Thomas Abraham <thomas.ab@xxxxxxxxxxx>
• [PATCH v6 0/6] cpufreq: use generic cpufreq drivers for exynos platforms
  • From: Thomas Abraham <thomas.ab@xxxxxxxxxxx>
• [Bug 77771] Intel P-State: Constantly changing CPU frequencies on idle system.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77771] Intel P-State: Constantly changing CPU frequencies on idle system.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77771] Intel P-State: Constantly changing CPU frequencies on idle system.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77771] Intel P-State: Constantly changing CPU frequencies on idle system.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77951] "intel_pstate: Set turbo VID for BayTrail" causes stall on Intel NUC DN2820FYKH
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77951] "intel_pstate: Set turbo VID for BayTrail" causes stall on Intel NUC DN2820FYKH
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77951] New: "intel_pstate: Set turbo VID for BayTrail" causes stall on Intel NUC DN2820FYKH
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77771] Intel P-State: Constantly changing CPU frequencies on idle system.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77771] Intel P-State: Constantly changing CPU frequencies on idle system.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77771] Intel P-State: Constantly changing CPU frequencies on idle system.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH 0/4] cpufreq: Use cpufreq-cpu0 driver for Exynos3250
  • From: Chanwoo Choi <cw00.choi@xxxxxxxxxxx>
• Re: [PATCH 0/4] cpufreq: Use cpufreq-cpu0 driver for Exynos3250
  • From: Thomas Abraham <ta.omasab@xxxxxxxxx>
• Re: [PATCH 0/4] cpufreq: Use cpufreq-cpu0 driver for Exynos3250
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• [Bug 77771] Intel P-State: Constantly changing CPU frequencies on idle system.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [PATCH 4/4] ARM: dts: Exynos: Add cpu clock table and armclk divider table for Exynos3250
  • From: Chanwoo Choi <cw00.choi@xxxxxxxxxxx>
• [PATCH 3/4] Documentation: devicetree: Add cpu clock configuration data binding for Exynos3250
  • From: Chanwoo Choi <cw00.choi@xxxxxxxxxxx>
• [PATCH 2/4] clk: samsung: Add support for cpu clocks of Exynos3250
  • From: Chanwoo Choi <cw00.choi@xxxxxxxxxxx>
• [PATCH 1/4] clk: samsung: exynos3250: Use cpu-clock provider type to support cpufreq
  • From: Chanwoo Choi <cw00.choi@xxxxxxxxxxx>
• [PATCH 0/4] cpufreq: Use cpufreq-cpu0 driver for Exynos3250
  • From: Chanwoo Choi <cw00.choi@xxxxxxxxxxx>
• [Bug 77771] New: Intel P-State: Constantly changing CPU frequencies on idle system.
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 77201] CPU online hangs, works when powernow-k8 is UN-loaded
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH 1/2] longhaul: Mark it as dangerous in Kconfig
  • From: Rafał Bilski <rafalbilski@xxxxxxxxxx>
• Re: [PATCH 2/2] e_powersaver: Require setting a module parameter to enable it
  • From: Rafał Bilski <rafalbilski@xxxxxxxxxx>
• [Bug 72361] AMD APU reset infinite
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH 2/2] e_powersaver: Require setting a module parameter to enable it
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [PATCH 1/2] longhaul: Mark it as dangerous in Kconfig
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• [Bug 72361] AMD APU reset infinite
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 72361] AMD APU reset infinite
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH 1/2] longhaul: Mark it as dangerous in Kconfig
  • From: Ben Hutchings <ben@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] longhaul: Mark it as dangerous in Kconfig
  • From: Dave Jones <davej@xxxxxxxxxx>
• [PATCH 2/2] e_powersaver: Require setting a module parameter to enable it
  • From: Ben Hutchings <ben@xxxxxxxxxxxxxxx>
• [PATCH 1/2] longhaul: Mark it as dangerous in Kconfig
  • From: Ben Hutchings <ben@xxxxxxxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• [patch NOT added to the 3.12 stable tree] MIPS/loongson2_cpufreq: Fix CPU clock rate setting
  • From: Jiri Slaby <jslaby@xxxxxxx>
• [PATCH] cpufreq: ppc-corenet-cpu-freq: do_div use quotient
  • From: Ed Swarthout <Ed.Swarthout@xxxxxxxxxxxxx>
• Re: [PATCH] cpufreq: ppc-corenet-cpu-freq: do_div use quotient
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [PATCH] cpufreq: ppc-corenet-cpu-freq: do_div use quotient
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• [PATCH 3.14 003/228] MIPS/loongson2_cpufreq: Fix CPU clock rate setting
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH] cpufreq: ppc-corenet-cpu-freq: do_div use quotient
  • From: Ed Swarthout <Ed.Swarthout@xxxxxxxxxxxxx>
• [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 75661] acpi-cpufreq cannot use lowest reported P-state (A8-4500M)
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 75661] acpi-cpufreq cannot use lowest reported P-state (A8-4500M)
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 72361] AMD APU reset infinite
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 69821] setting CONFIG_HZ_PERIODIC locks cpu at the lowest frequency using ONDEMAND
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 65501] Blind angle of 1% between up_threshold and down_threshold
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 62551] The system freezes for a moment when the CPU scaling is enabled
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: Performance regression in v3.14
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: Performance regression in v3.14
  • From: Johan Hovold <jhovold@xxxxxxxxx>
• Re: Performance regression in v3.14
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Performance regression in v3.14
  • From: Yuyang Du <yuyang.du@xxxxxxxxx>
• [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• RE: Performance regression in v3.14
  • From: "Doug Smythies" <dsmythies@xxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: Performance regression in v3.14
  • From: Yuyang Du <yuyang.du@xxxxxxxxx>
• Re: Performance regression in v3.14
  • From: Johan Hovold <jhovold@xxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Mike Turquette <mturquette@xxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [PATCH v4 4/8] Documentation: devicetree: add cpu clock configuration data binding for Exynos4/5
  • From: Tomasz Figa <tomasz.figa@xxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [PATCH v5 7/7] cpufreq: exynos: remove all exynos specific cpufreq driver support
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [PATCH v5 6/7] ARM: Exynos: switch to using generic cpufreq-cpu0 driver
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [PATCH v5 1/7] cpufreq: cpufreq-cpu0: allow use of optional boost mode frequencies
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [PATCH v4 4/8] Documentation: devicetree: add cpu clock configuration data binding for Exynos4/5
  • From: Thomas Abraham <ta.omasab@xxxxxxxxx>
• RE: [PATCH v5 0/7] cpufreq: use cpufreq-cpu0 driver for exynos based platforms
  • From: Kukjin Kim <kgene.kim@xxxxxxxxxxx>
• Re: [PATCH v5 0/7] cpufreq: use cpufreq-cpu0 driver for exynos based platforms
  • From: Tomasz Figa <tomasz.figa@xxxxxxxxx>
• Re: [PATCH v5 0/7] cpufreq: use cpufreq-cpu0 driver for exynos based platforms
  • From: Kukjin Kim <kgene.kim@xxxxxxxxxxx>
• [Bug 72361] AMD APU reset infinite
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• Re: [PATCH v2] cpufreq: s5pv210: drop check for CONFIG_PM_VERBOSE
  • From: Sachin Kamat <sachin.kamat@xxxxxxxxxx>
• Re: [PATCH v2] cpufreq: s5pv210: drop check for CONFIG_PM_VERBOSE
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• [PATCH v2] cpufreq: s5pv210: drop check for CONFIG_PM_VERBOSE
  • From: Paul Bolle <pebolle@xxxxxxxxxx>
• Re: [PATCH v4 3/8] clk: samsung: add infrastructure to register cpu clocks
  • From: Tomasz Figa <t.figa@xxxxxxxxxxx>
• Re: [PATCH v4 3/8] clk: samsung: add infrastructure to register cpu clocks
  • From: Thomas Abraham <ta.omasab@xxxxxxxxx>
• [PATCH v5 7/7] cpufreq: exynos: remove all exynos specific cpufreq driver support
  • From: Thomas Abraham <thomas.ab@xxxxxxxxxxx>
• [PATCH v5 6/7] ARM: Exynos: switch to using generic cpufreq-cpu0 driver
  • From: Thomas Abraham <thomas.ab@xxxxxxxxxxx>
• [PATCH v5 5/7] ARM: dts: Exynos: add cpu nodes, opp and cpu clock configuration data
  • From: Thomas Abraham <thomas.ab@xxxxxxxxxxx>
• [PATCH v5 4/7] clk: exynos: use cpu-clock provider type to represent arm clock
  • From: Thomas Abraham <thomas.ab@xxxxxxxxxxx>
• [PATCH v5 3/7] Documentation: devicetree: add cpu clock configuration data binding for Exynos4/5
  • From: Thomas Abraham <thomas.ab@xxxxxxxxxxx>
• [PATCH v5 2/7] clk: samsung: add infrastructure to register cpu clocks
  • From: Thomas Abraham <thomas.ab@xxxxxxxxxxx>
• [PATCH v5 1/7] cpufreq: cpufreq-cpu0: allow use of optional boost mode frequencies
  • From: Thomas Abraham <thomas.ab@xxxxxxxxxxx>
• [PATCH v5 0/7] cpufreq: use cpufreq-cpu0 driver for exynos based platforms
  • From: Thomas Abraham <thomas.ab@xxxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Mike Turquette <mturquette@xxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• Re: [PATCH] cpufreq: s5pv210: remove unused call of pr_err()
  • From: Sachin Kamat <sachin.kamat@xxxxxxxxxx>
• Re: [PATCH] cpufreq: s5pv210: remove unused call of pr_err()
  • From: Paul Bolle <pebolle@xxxxxxxxxx>
• Re: [PATCH] cpufreq: s5pv210: remove unused call of pr_err()
  • From: Sachin Kamat <sachin.kamat@xxxxxxxxxx>
• Re: [PATCH] cpufreq: s5pv210: remove unused call of pr_err()
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [PATCH] cpufreq: s5pv210: remove unused call of pr_err()
  • From: Sachin Kamat <sachin.kamat@xxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Mike Turquette <mturquette@xxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• [PATCH] cpufreq: s5pv210: remove unused call of pr_err()
  • From: Paul Bolle <pebolle@xxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• 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: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [PATCH v3] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end
  • From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
• Re: Performance regression in v3.14
  • From: Johan Hovold <jhovold@xxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Stephen Boyd <sboyd@xxxxxxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• RE: [PATCH v3] cpufreq: exynos: Fix the compile error
  • From: Kukjin Kim <kgene.kim@xxxxxxxxxxx>
• Re: [PATCH v3] cpufreq: exynos: Fix the compile error
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [PATCH] cpufreq: powernv: make local function static
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [PATCH] cpufreq: remove race while accessing cur_policy
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• [PATCH] cpufreq: remove race while accessing cur_policy
  • From: Bibek Basu <bbasu@xxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• Re: [PATCH] cpufreq: cpu0: drop wrong devm usage
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [PATCH v4 0/8] cpufreq: use cpufreq-cpu0 driver for exynos based platforms
  • From: Tomasz Figa <tomasz.figa@xxxxxxxxx>
• Re: [PATCH v4 7/8] ARM: Exynos: switch to using generic cpufreq-cpu0 driver
  • From: Tomasz Figa <tomasz.figa@xxxxxxxxx>
• Re: [PATCH v4 4/8] Documentation: devicetree: add cpu clock configuration data binding for Exynos4/5
  • From: Tomasz Figa <tomasz.figa@xxxxxxxxx>
• Re: [PATCH v4 5/8] clk: exynos: use cpu-clock provider type to represent arm clock.
  • From: Tomasz Figa <tomasz.figa@xxxxxxxxx>
• Re: [PATCH v3] cpufreq: exynos: Fix the compile error
  • From: Kukjin Kim <kgene.kim@xxxxxxxxxxx>
• Re: [PATCH v3] cpufreq: exynos: Fix the compile error
  • From: Tomasz Figa <tomasz.figa@xxxxxxxxx>
• Re: [PATCH v3] cpufreq: exynos: Fix the compile error
  • From: Tomasz Figa <tomasz.figa@xxxxxxxxx>
• Re: [PATCH v3] cpufreq: exynos: Fix the compile error
  • From: Kukjin Kim <kgene.kim@xxxxxxxxxxx>
• Re: [PATCH v3] cpufreq: exynos: Fix the compile error
  • From: Kukjin Kim <kgene.kim@xxxxxxxxxxx>
• Re: [PATCH v4 4/8] Documentation: devicetree: add cpu clock configuration data binding for Exynos4/5
  • From: Tomasz Figa <tomasz.figa@xxxxxxxxx>
• Re: [PATCH v4 6/8] ARM: dts: Exynos: add cpu nodes, opp and cpu clock configuration data
  • From: Tomasz Figa <tomasz.figa@xxxxxxxxx>
• Re: [PATCH v3] cpufreq: exynos: Fix the compile error
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [PATCH] cpufreq: cpu0: drop wrong devm usage
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [PATCH v4 3/8] clk: samsung: add infrastructure to register cpu clocks
  • From: Tomasz Figa <t.figa@xxxxxxxxxxx>
• Re: [PATCH v4 2/8] clk: samsung: change scope of samsung clock lock to global
  • From: Tomasz Figa <t.figa@xxxxxxxxxxx>
• Re: [PATCH] cpufreq: cpu0: drop wrong devm usage
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [PATCH v3] cpufreq: exynos: Fix the compile error
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• RE: [PATCH v3] cpufreq: exynos: Fix the compile error
  • From: Kukjin Kim <kgene.kim@xxxxxxxxxxx>
• [PATCH] cpufreq: cpu0: drop wrong devm usage
  • From: Lucas Stach <l.stach@xxxxxxxxxxxxxx>
• [PATCH v3] cpufreq: exynos: Fix the compile error
  • From: Jonghwan Choi <jhbird.choi@xxxxxxxxxxx>
• RE: [PATCH v2] cpufreq: exynos: Fix the compile error
  • From: Jonghwan Choi <jhbird.choi@xxxxxxxxxxx>
• Re: [PATCH v2] cpufreq: exynos: Fix the compile error
  • From: Tomasz Figa <tomasz.figa@xxxxxxxxx>
• RE: [PATCH] cpufreq: exynos: Fix the compile error
  • From: Kukjin Kim <kgene.kim@xxxxxxxxxxx>
• RE: [PATCH] cpufreq: exynos: Fix the compile error
  • From: Kukjin Kim <kgene.kim@xxxxxxxxxxx>
• [PATCH v2] cpufreq: exynos: Fix the compile error
  • From: Jonghwan Choi <jhbird.choi@xxxxxxxxxxx>
• Re: [PATCH] cpufreq: exynos: Fix the compile error
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [PATCH] cpufreq: exynos: Fix the compile error
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• [PATCH] cpufreq: exynos: Fix the compile error
  • From: Jonghwan Choi <jhbird.choi@xxxxxxxxxxx>
• Re: [PATCH v4 5/8] clk: exynos: use cpu-clock provider type to represent arm clock.
  • From: Thomas Abraham <ta.omasab@xxxxxxxxx>
• Re: [PATCH v4 3/8] clk: samsung: add infrastructure to register cpu clocks
  • From: Thomas Abraham <ta.omasab@xxxxxxxxx>
• Re: [PATCH v4 3/8] clk: samsung: add infrastructure to register cpu clocks
  • From: Doug Anderson <dianders@xxxxxxxxxxxx>
• Re: [PATCH v4 3/8] clk: samsung: add infrastructure to register cpu clocks
  • From: Heiko Stübner <heiko@xxxxxxxxx>
• Re: [PATCH v4 3/8] clk: samsung: add infrastructure to register cpu clocks
  • From: Doug Anderson <dianders@xxxxxxxxxxxx>
• Re: [PATCH v4 3/8] clk: samsung: add infrastructure to register cpu clocks
  • From: Heiko Stübner <heiko@xxxxxxxxx>
• Re: [PATCH v4 3/8] clk: samsung: add infrastructure to register cpu clocks
  • From: Doug Anderson <dianders@xxxxxxxxxxxx>
• Re: Format of patches
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• Re: [RFC PATCH 0/5] Frequency resolution in CCF vs. cpufreq
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• Re: [RFC PATCH 0/5] Frequency resolution in CCF vs. cpufreq
  • From: Sören Brinkmann <soren.brinkmann@xxxxxxxxxx>
• Re: Format of patches (was: [PATCH 1/2] speedstep-smi: enable interrupts when waiting)
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: Format of patches (was: [PATCH 1/2] speedstep-smi: enable interrupts when waiting)
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [RFC PATCH 0/5] Frequency resolution in CCF vs. cpufreq
  • From: Nishanth Menon <nm@xxxxxx>
• Re: Format of patches (was: [PATCH 1/2] speedstep-smi: enable interrupts when waiting)
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Format of patches (was: [PATCH 1/2] speedstep-smi: enable interrupts when waiting)
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v4 5/8] clk: exynos: use cpu-clock provider type to represent arm clock.
  • From: Thomas Abraham <ta.omasab@xxxxxxxxx>
• Re: [PATCH v4 5/8] clk: exynos: use cpu-clock provider type to represent arm clock.
  • From: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
• Re: [PATCH v4 5/8] clk: exynos: use cpu-clock provider type to represent arm clock.
  • From: Thomas Abraham <ta.omasab@xxxxxxxxx>
• Re: [RFC PATCH 0/5] Frequency resolution in CCF vs. cpufreq
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [RFC PATCH 0/5] Frequency resolution in CCF vs. cpufreq
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [PATCH 1/2] speedstep-smi: enable interrupts when waiting
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• [RFC PATCH 1/5] cpufreq: stats: Allow small rounding errors
  • From: Soren Brinkmann <soren.brinkmann@xxxxxxxxxx>
• [RFC PATCH 3/5] cpufreq: cpu0: Use clk_round_rate_nearest()
  • From: Soren Brinkmann <soren.brinkmann@xxxxxxxxxx>
• [RFC PATCH 2/5] clk: Introduce 'clk_round_rate_nearest()'
  • From: Soren Brinkmann <soren.brinkmann@xxxxxxxxxx>
• [RFC PATCH 4/5] ARM: zynq: dt: Use properly rounded frequencies in OPPs
  • From: Soren Brinkmann <soren.brinkmann@xxxxxxxxxx>
• [RFC PATCH 5/5] net: macb: Use clk_round_rate_nearest() API
  • From: Soren Brinkmann <soren.brinkmann@xxxxxxxxxx>
• [RFC PATCH 0/5] Frequency resolution in CCF vs. cpufreq
  • From: Soren Brinkmann <soren.brinkmann@xxxxxxxxxx>
• Re: [PATCH v4 5/8] clk: exynos: use cpu-clock provider type to represent arm clock.
  • From: Mike Turquette <mturquette@xxxxxxxxxx>
• Re: [PATCH v4 7/8] ARM: Exynos: switch to using generic cpufreq-cpu0 driver
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• [PATCH 2/2] speedstep: clean up interrupt disabling
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/2] speedstep-smi: enable interrupts when waiting
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• 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: Thomas Abraham <ta.omasab@xxxxxxxxx>
• Re: [PATCH v4 7/8] ARM: Exynos: switch to using generic cpufreq-cpu0 driver
  • From: Thomas Abraham <ta.omasab@xxxxxxxxx>
• Re: [PATCH v4 7/8] ARM: Exynos: switch to using generic cpufreq-cpu0 driver
  • From: Sudeep Holla <sudeep.holla@xxxxxxx>
• Re: [PATCH v4 7/8] ARM: Exynos: switch to using generic cpufreq-cpu0 driver
  • From: Thomas Abraham <ta.omasab@xxxxxxxxx>
• Re: [PATCH v4 8/8] cpufreq: exynos: remove all exynos specific cpufreq driver support
  • From: Thomas Abraham <ta.omasab@xxxxxxxxx>
• Re: [PATCH v4 1/8] cpufreq: cpufreq-cpu0: allow use of optional boost mode frequencies
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [PATCH v4 7/8] ARM: Exynos: switch to using generic cpufreq-cpu0 driver
  • From: Rob Herring <robherring2@xxxxxxxxx>
• Re: [PATCH v4 1/8] cpufreq: cpufreq-cpu0: allow use of optional boost mode frequencies
  • From: Thomas Abraham <ta.omasab@xxxxxxxxx>
• Re: [PATCH v4 2/8] clk: samsung: change scope of samsung clock lock to global
  • From: Thomas Abraham <ta.omasab@xxxxxxxxx>
• Re: [PATCH v4 7/8] ARM: Exynos: switch to using generic cpufreq-cpu0 driver
  • From: Arnd Bergmann <arnd@xxxxxxxx>