Linux CPU Freq
[Prev Page][Next Page]
- [PATCH V2 6/8] ARM: dts: OMAP4460: Add CPU OPP table
- From: Nishanth Menon <nm@xxxxxx>
- RE: CPU power management bug -- CPU bound task fails to raise CPU frequency
- From: Bruce Dawson <bruced@xxxxxxxxxxxxxxxxx>
- [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: CPU power management bug -- CPU bound task fails to raise CPU frequency
- From: Vincent Guittot <vincent.guittot@xxxxxxxxxx>
- [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH v3 1/3] ARM: shmobile: sh73a0: wait for completion when kicking the clock
- From: Magnus Damm <magnus.damm@xxxxxxxxx>
- Re: [PATCH v3 1/3] ARM: shmobile: sh73a0: wait for completion when kicking the clock
- From: Simon Horman <horms@xxxxxxxxxxxx>
- RE: CPU power management bug -- CPU bound task fails to raise CPU frequency
- From: Bruce Dawson <bruced@xxxxxxxxxxxxxxxxx>
- [Bug 50721] CPU freqs stay stuck at max after reboot with on-demand governor set - i7-2630QM
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- RE: CPU power management bug -- CPU bound task fails to raise CPU frequency
- From: Bruce Dawson <bruced@xxxxxxxxxxxxxxxxx>
- [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: CPU power management bug -- CPU bound task fails to raise CPU frequency
- From: Vincent Guittot <vincent.guittot@xxxxxxxxxx>
- Re: [PATCH V4 1/4] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: amit kachhap <amit.kachhap@xxxxxxxxx>
- [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 55411] New: sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH] cpufreq: Fix unsigned variable being checked for negative value
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: Fix unsigned variable being checked for negative value
- From: Shawn Guo <shawn.guo@xxxxxxxxxx>
- [PATCH] cpufreq: Fix unsigned variable being checked for negative value
- From: Jonghwan Choi <jhbird.choi@xxxxxxxxxxx>
- RE: CPU power management bug -- CPU bound task fails to raise CPU frequency
- From: Bruce Dawson <bruced@xxxxxxxxxxxxxxxxx>
- Re: CPU power management bug -- CPU bound task fails to raise CPU frequency
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: CPU power management bug -- CPU bound task fails to raise CPU frequency
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- CPU power management bug -- CPU bound task fails to raise CPU frequency
- From: Bruce Dawson <bruced@xxxxxxxxxxxxxxxxx>
- Re: [PATCH 2/8] ARM: dts: OMAP36xx: move CPU OPP tables to device tree
- From: Nishanth Menon <nm@xxxxxx>
- Re: [PATCH 0/8] ARM: OMAP3+: Switch to use DT based cpu0-cpufreq driver
- From: Nishanth Menon <nm@xxxxxx>
- Re: [PATCH 2/8] ARM: dts: OMAP36xx: move CPU OPP tables to device tree
- From: Jon Hunter <jon-hunter@xxxxxx>
- Re: [PATCH 0/8] ARM: OMAP3+: Switch to use DT based cpu0-cpufreq driver
- From: Jon Hunter <jon-hunter@xxxxxx>
- Re: [PATCH 2/8] ARM: dts: OMAP36xx: move CPU OPP tables to device tree
- From: Nishanth Menon <nm@xxxxxx>
- Re: [PATCH 2/8] ARM: dts: OMAP36xx: move CPU OPP tables to device tree
- From: Jon Hunter <jon-hunter@xxxxxx>
- Re: [PATCH 8/8] cpufreq: omap: remove omap-cpufreq
- From: Nishanth Menon <nm@xxxxxx>
- Re: [PATCH 0/8] ARM: OMAP3+: Switch to use DT based cpu0-cpufreq driver
- From: Nishanth Menon <nm@xxxxxx>
- Re: [PATCH 6/8] ARM: dts: OMAP446x: move CPU OPP tables to device tree
- From: Nishanth Menon <nm@xxxxxx>
- Re: [PATCH 2/8] ARM: dts: OMAP36xx: move CPU OPP tables to device tree
- From: Nishanth Menon <nm@xxxxxx>
- Re: [PATCH 0/8] ARM: OMAP3+: Switch to use DT based cpu0-cpufreq driver
- From: Nishanth Menon <nm@xxxxxx>
- [Bug 55261] down_threshold is missing
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: cpufreq cowork with scheduler
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [Bug 55261] down_threshold is missing
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- cpufreq cowork with scheduler
- From: Chao Xie <xiechao.mail@xxxxxxxxx>
- [Bug 55261] New: down_threshold is missing
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH 0/8] ARM: OMAP3+: Switch to use DT based cpu0-cpufreq driver
- From: Santosh Shilimkar <santosh.shilimkar@xxxxxx>
- Re: [PATCH 8/8] cpufreq: omap: remove omap-cpufreq
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 6/8] ARM: dts: OMAP446x: move CPU OPP tables to device tree
- From: Jon Hunter <jon-hunter@xxxxxx>
- Re: [PATCH 2/8] ARM: dts: OMAP36xx: move CPU OPP tables to device tree
- From: Jon Hunter <jon-hunter@xxxxxx>
- Re: [PATCH 1/8] ARM: dts: OMAP34xx: move CPU OPP tables to device tree
- From: Jon Hunter <jon-hunter@xxxxxx>
- Re: [PATCH 0/8] ARM: OMAP3+: Switch to use DT based cpu0-cpufreq driver
- From: Jon Hunter <jon-hunter@xxxxxx>
- [PATCH 1/8] ARM: dts: OMAP34xx: move CPU OPP tables to device tree
- From: Nishanth Menon <nm@xxxxxx>
- [PATCH 2/8] ARM: dts: OMAP36xx: move CPU OPP tables to device tree
- From: Nishanth Menon <nm@xxxxxx>
- [PATCH 3/8] ARM: dts: OMAP3: use twl4030 vdd1 regulator for CPU
- From: Nishanth Menon <nm@xxxxxx>
- [PATCH 5/8] ARM: dts: omap4-panda: move generic sections to panda-common
- From: Nishanth Menon <nm@xxxxxx>
- [PATCH 6/8] ARM: dts: OMAP446x: move CPU OPP tables to device tree
- From: Nishanth Menon <nm@xxxxxx>
- [PATCH 8/8] cpufreq: omap: remove omap-cpufreq
- From: Nishanth Menon <nm@xxxxxx>
- [PATCH 7/8] ARM: OMAP3+: use cpu0-cpufreq driver
- From: Nishanth Menon <nm@xxxxxx>
- [PATCH 4/8] ARM: dts: OMAP443x: move CPU OPP tables to device tree
- From: Nishanth Menon <nm@xxxxxx>
- [PATCH 0/8] ARM: OMAP3+: Switch to use DT based cpu0-cpufreq driver
- From: Nishanth Menon <nm@xxxxxx>
- [Bug 50721] CPU freqs stay stuck at max after reboot with on-demand governor set - i7-2630QM
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH V3 4/4] cpufreq: Add Kconfig option to enable/disable have_multiple_policies
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V3 4/4] cpufreq: Add Kconfig option to enable/disable have_multiple_policies
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH v4 0/2] cpufreq: cpufreq_driver_lock is hot on large systems
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- Re: [PATCH 1/2] cpufreq: cpufreq-cpu0: support for clock which are not in DT yet.
- From: Nishanth Menon <nm@xxxxxx>
- Re: [PATCH 2/2] cpufreq: cpufreq-cpu0: provide compatibility string for DT matchup
- From: Benoit Cousson <b-cousson@xxxxxx>
- RE: [PATCH 1/2] cpufreq: cpufreq-cpu0: support for clock which are not in DT yet.
- From: "J, KEERTHY" <j-keerthy@xxxxxx>
- Re: [PATCH 2/2] cpufreq: cpufreq-cpu0: provide compatibility string for DT matchup
- From: Nishanth Menon <nm@xxxxxx>
- Re: [PATCH 1/2] cpufreq: cpufreq-cpu0: support for clock which are not in DT yet.
- From: Nishanth Menon <nm@xxxxxx>
- Re: [PATCH 2/2] cpufreq: cpufreq-cpu0: provide compatibility string for DT matchup
- From: Santosh Shilimkar <santosh.shilimkar@xxxxxx>
- Re: [PATCH 2/2] cpufreq: cpufreq-cpu0: provide compatibility string for DT matchup
- From: Benoit Cousson <b-cousson@xxxxxx>
- Re: [PATCH 1/2] cpufreq: cpufreq-cpu0: support for clock which are not in DT yet.
- From: Benoit Cousson <b-cousson@xxxxxx>
- [Bug 55091] cpufreq governors woks crazy
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH V4 1/4] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V4 1/4] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: Amit Daniel Kachhap <amit.daniel@xxxxxxxxxxx>
- [PATCH V4 3/4] arm: exynos: Enable OPP library support for exynos5440
- From: Amit Daniel Kachhap <amit.daniel@xxxxxxxxxxx>
- [PATCH V4 4/4] dts: Add cpufreq controller node for Exynos5440 SoC
- From: Amit Daniel Kachhap <amit.daniel@xxxxxxxxxxx>
- [PATCH V4 2/4] cpufreq: exynos: Remove error return even if no soc is found
- From: Amit Daniel Kachhap <amit.daniel@xxxxxxxxxxx>
- [PATCH V4 0/4] cpufreq: exynos5440: support for cpufreq driver
- From: Amit Daniel Kachhap <amit.daniel@xxxxxxxxxxx>
- Re: [PATCH 2/2] cpufreq: cpufreq-cpu0: provide compatibility string for DT matchup
- From: Shawn Guo <shawn.guo@xxxxxxxxxx>
- Re: [PATCH 1/2] cpufreq: cpufreq-cpu0: support for clock which are not in DT yet.
- From: Shawn Guo <shawn.guo@xxxxxxxxxx>
- Re: [PATCH 2/2] cpufreq: cpufreq-cpu0: provide compatibility string for DT matchup
- From: Santosh Shilimkar <santosh.shilimkar@xxxxxx>
- Re: [PATCH 1/2] cpufreq: cpufreq-cpu0: support for clock which are not in DT yet.
- From: Santosh Shilimkar <santosh.shilimkar@xxxxxx>
- Re: [PATCH V3 4/4] cpufreq: Add Kconfig option to enable/disable have_multiple_policies
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/3] workqueue: define mod_scheduled_delayed_work[_on]() helpers
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] kirkwood: fix coccicheck warnings
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH] kirkwood: fix coccicheck warnings
- From: Zhang Rui <rui.zhang@xxxxxxxxx>
- Re: [PATCH V3 4/4] cpufreq: Add Kconfig option to enable/disable have_multiple_policies
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 1/3] workqueue: define mod_scheduled_delayed_work[_on]() helpers
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH v4 0/2] cpufreq: cpufreq_driver_lock is hot on large systems
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- [PATCH 0/2] cpufreq: cpufreq-cpu0: cleanups around DT usage
- From: Nishanth Menon <nm@xxxxxx>
- [PATCH 1/2] cpufreq: cpufreq-cpu0: support for clock which are not in DT yet.
- From: Nishanth Menon <nm@xxxxxx>
- [PATCH 2/2] cpufreq: cpufreq-cpu0: provide compatibility string for DT matchup
- From: Nishanth Menon <nm@xxxxxx>
- [Bug 55091] New: cpufreq governors woks crazy
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH] kirkwood: fix coccicheck warnings
- From: Silviu Popescu <silviupopescu1990@xxxxxxxxx>
- Re: [PATCH] kirkwood: fix coccicheck warnings
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 3/3 linux-next] cpufreq: conservative: Use an inline function to evaluate freq_target
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH v2] kirkwood: fix coccicheck warnings
- From: Daniel Lezcano <daniel.lezcano@xxxxxxxxxx>
- [PATCH v2] kirkwood: fix coccicheck warnings
- From: Silviu-Mihai Popescu <silviupopescu1990@xxxxxxxxx>
- Re: [PATCH] kirkwood: fix coccicheck warnings
- From: Zhang Rui <rui.zhang@xxxxxxxxx>
- Re: [PATCH] kirkwood: fix coccicheck warnings
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] kirkwood: fix coccicheck warnings
- From: Jason Cooper <jason@xxxxxxxxxxxxxx>
- Re: [PATCH] kirkwood: fix coccicheck warnings
- From: Andrew Lunn <andrew@xxxxxxx>
- [PATCH] kirkwood: fix coccicheck warnings
- From: Silviu-Mihai Popescu <silviupopescu1990@xxxxxxxxx>
- Re: [PATCH V3 1/4] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: amit kachhap <amit.kachhap@xxxxxxxxx>
- Re: [PATCH V3 1/4] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: amit kachhap <amit.kachhap@xxxxxxxxx>
- Re: [PATCH V3 1/4] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: amit kachhap <amit.kachhap@xxxxxxxxx>
- Re: [PATCH V2] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V2] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Francesco Lavra <francescolavra.fl@xxxxxxxxx>
- Re: [PATCH V3 1/4] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V2] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V2] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
- Re: [PATCH V2] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V2] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
- [PATCH V2] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V3 1/4] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- Re: [PATCH V3 1/4] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: Sylwester Nawrocki <s.nawrocki@xxxxxxxxxxx>
- Re: [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- [Bug 54221] ondemand cpufeq governor do not notice Node Manager power limit change
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [PATCH V3 1/4] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: Amit Daniel Kachhap <amit.daniel@xxxxxxxxxxx>
- [PATCH V3 2/4] cpufreq: exynos: Remove error return even if no soc is found
- From: Amit Daniel Kachhap <amit.daniel@xxxxxxxxxxx>
- [PATCH V3 4/4] dts: Add cpufreq controller node for Exynos5440 SoC
- From: Amit Daniel Kachhap <amit.daniel@xxxxxxxxxxx>
- [PATCH V3 3/4] arm: exynos: Enable OPP library support for exynos5440
- From: Amit Daniel Kachhap <amit.daniel@xxxxxxxxxxx>
- Re: [PATCH 2/2] cpufreq/intel_pstate: Fix intel_pstate_init() error path
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Olof Johansson <olof@xxxxxxxxx>
- Re: [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Olof Johansson <olof@xxxxxxxxx>
- Re: [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Harvey Harrison <harvey.harrison@xxxxxxxxx>
- Re: [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/3 linux-next] cpufreq: conservative: Fix the logic in frequency decrease checking
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH 2/3 linux-next] cpufreq: conservative: Fix the logic in frequency decrease checking
- From: David C Niemi <dniemi@xxxxxxxxxxxx>
- Re: [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- [PATCH 2/2] cpufreq/intel_pstate: Fix intel_pstate_init() error path
- From: dirk.brandewie@xxxxxxxxx
- Re: [PATCH 3/3 linux-next] cpufreq: conservative: Use an inline function to evaluate freq_target
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: Dynamic cpufreq_frequency_table?
- From: Guru Prasad <gurupras@xxxxxxxxxxx>
- Re: [PATCH 3/3 linux-next] cpufreq: conservative: Use an inline function to evaluate freq_target
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH 0/2] v3.9-rc1 fixes for intel_pstate driver
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/2] cpufreq/intel_pstate: Fix intel_pstate_init() error path
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 3/3 linux-next] cpufreq: conservative: Use an inline function to evaluate freq_target
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 3/3 linux-next] cpufreq: conservative: Use an inline function to evaluate freq_target
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/3 linux-next] cpufreq: conservative: Fix the logic in frequency decrease checking
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/3 linux-next] cpufreq: conservative: Fix sampling_down_factor functionality
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH linux-next] cpufreq: conservative: Fix sampling_down_factor functionality
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V2 1/4] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V2 1/4] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: amit kachhap <amit.kachhap@xxxxxxxxx>
- Re: Dynamic cpufreq_frequency_table?
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 2/2] cpufreq/intel_pstate: Fix intel_pstate_init() error path
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 1/2] cpufreq/intel_pstate: Do not load on VM that do not report max P state.
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 0/2] v3.9-rc1 fixes for intel_pstate driver
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 2/3 linux-next] cpufreq: conservative: Fix the logic in frequency decrease checking
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH 3/3 linux-next] cpufreq: conservative: Use an inline function to evaluate freq_target
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH 1/3 linux-next] cpufreq: conservative: Fix sampling_down_factor functionality
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH linux-next] cpufreq: conservative: Fix sampling_down_factor functionality
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH linux-next] cpufreq: conservative: Fix sampling_down_factor functionality
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: Dynamic cpufreq_frequency_table?
- From: Guru Prasad <gurupras@xxxxxxxxxxx>
- Re: Dynamic cpufreq_frequency_table?
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Dynamic cpufreq_frequency_table?
- From: Guru Prasad <gurupras@xxxxxxxxxxx>
- Re: [PATCH linux-next] cpufreq: conservative: Fix sampling_down_factor functionality
- From: David C Niemi <dniemi@xxxxxxxxxxxx>
- Re: [PATCH linux-next] cpufreq: conservative: Fix sampling_down_factor functionality
- From: David C Niemi <dniemi@xxxxxxxxxxxx>
- Re: [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- Re: [PATCH linux-next] cpufreq: conservative: Fix sampling_down_factor functionality
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH linux-next] cpufreq: conservative: Fix sampling_down_factor functionality
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V2 1/4] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH linux-next] cpufreq: conservative: Fix sampling_down_factor functionality
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH linux-next] cpufreq: conservative: Fix sampling_down_factor functionality
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [Bug 54761] New: Variable cpu frequency causes to loose performance
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [PATCH V2 2/2] cpufreq: governors: Avoid unnecessary per cpu timer interrupts
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V2 1/2] cpufreq: ondemand: Don't update sample_type if we don't evaluate load again
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V2 0/2] cpufreq: governors: Avoid unnecessary per cpu timer interrupts
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V3 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V3 1/4] cpufreq: Add per policy governor-init/exit infrastructure
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V3 2/4] cpufreq: governor: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V3 3/4] cpufreq: Get rid of "struct global_attr"
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V3 4/4] cpufreq: Add Kconfig option to enable/disable have_multiple_policies
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V2 1/4] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: Amit Daniel Kachhap <amit.daniel@xxxxxxxxxxx>
- [PATCH V2 3/4] arm: exynos: Enable OPP library support for exynos5440
- From: Amit Daniel Kachhap <amit.daniel@xxxxxxxxxxx>
- [PATCH V2 4/4] dts: Add cpufreq controller node for Exynos5440 SoC
- From: Amit Daniel Kachhap <amit.daniel@xxxxxxxxxxx>
- [PATCH V2 2/4] cpufreq: exynos: Remove error return even if no soc is found
- From: Amit Daniel Kachhap <amit.daniel@xxxxxxxxxxx>
- Re: [PATCH/RFC v2 0/2] CPUFreq for kzm9g
- From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
- Divide error in intel_pstate_set_policy
- From: Josh Boyer <jwboyer@xxxxxxxxxx>
- Re: [PATCH v2 linux-next] cpufreq: governors: Calculate iowait time only when necessary
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v3 1/3] ARM: shmobile: sh73a0: wait for completion when kicking the clock
- From: Simon Horman <horms@xxxxxxxxxxxx>
- Re: [PATCH v2 linux-next] cpufreq: governors: Calculate iowait time only when necessary
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH v3 0/3] CPUFreq for kzm9g
- From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
- [PATCH/RFC v3 3/3] ARM: shmobile: kzm9g-reference: add CPUFreq support
- From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
- [PATCH/RFC v3 2/3] ARM: shmobile: sh73a0: add support for adjusting CPU frequency
- From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
- [PATCH v3 1/3] ARM: shmobile: sh73a0: wait for completion when kicking the clock
- From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
- Re: [PATCH linux-next] cpufreq: governors: Calculate iowait time only when necessary
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH -next 3/3] cpufreq: conservative: Fix relation when decreasing frequency
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH -next 3/3] cpufreq: conservative: Fix relation when decreasing frequency
- From: Namhyung Kim <namhyung@xxxxxxxxxx>
- Re: [PATCH -next 3/3] cpufreq: conservative: Fix relation when decreasing frequency
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH -next 3/3] cpufreq: conservative: Fix relation when decreasing frequency
- From: Namhyung Kim <namhyung@xxxxxxxxxx>
- [PATCH -next 2/3] cpufreq: conservative: Break out earlier on the lowest frequency
- From: Namhyung Kim <namhyung@xxxxxxxxxx>
- [PATCH -next 1/3] cpufreq: Fix a typo in comment
- From: Namhyung Kim <namhyung@xxxxxxxxxx>
- [Bug 54221] ondemand cpufeq governor do not notice Node Manager power limit change
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 54221] ondemand cpufeq governor do not notice Node Manager power limit change
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 54221] ondemand cpufeq governor do not notice Node Manager power limit change
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 54541] Cpu frequency don't work in conky with kernel 3.9.0.0.rc0.git8
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [PATCH linux-next] cpufreq: governors: Calculate iowait time only when necessary
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH 1/3] workqueue: define mod_scheduled_delayed_work[_on]() helpers
- From: Tejun Heo <tj@xxxxxxxxxx>
- Re: [PATCH 1/3] workqueue: define mod_scheduled_delayed_work[_on]() helpers
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/3] workqueue: define mod_scheduled_delayed_work[_on]() helpers
- From: Tejun Heo <tj@xxxxxxxxxx>
- Re: [PATCH 1/3] workqueue: define mod_scheduled_delayed_work[_on]() helpers
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 2/3] cpufreq: ondemand: Don't update sample_type if we don't evaluate load again
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 3/3] cpufreq: governors: Avoid unnecessary per cpu timer interrupts
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 1/3] workqueue: define mod_scheduled_delayed_work[_on]() helpers
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [Bug 54541] Cpu frequency don't work in conky with kernel 3.9.0.0.rc0.git8
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 54541] Cpu frequency don't work in conky with kernel 3.9.0.0.rc0.git8
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 54541] New: Cpu frequency don't work in conky with kernel 3.9.0.0.rc0.git8
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [RFC] cpufreq: governor: Set MIN_LATENCY_MULTIPLIER to 20
- From: Thomas Renninger <trenn@xxxxxxx>
- Re: [PATCH 1/4] ARM: shmobile: sh73a0: fix Z and ZG clock hierarchy
- From: Simon Horman <horms@xxxxxxxxxxxx>
- Re: [PATCH/RFC v2 0/2] CPUFreq for kzm9g
- From: Magnus Damm <magnus.damm@xxxxxxxxx>
- Re: [RFC] cpufreq: governor: Set MIN_LATENCY_MULTIPLIER to 20
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [RFC] cpufreq: governor: Set MIN_LATENCY_MULTIPLIER to 20
- From: Thomas Renninger <trenn@xxxxxxx>
- [RFC] cpufreq: governor: Set MIN_LATENCY_MULTIPLIER to 20
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/4] ARM: shmobile: sh73a0: fix Z and ZG clock hierarchy
- From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
- Re: [PATCH 1/4] ARM: shmobile: sh73a0: fix Z and ZG clock hierarchy
- From: Simon Horman <horms@xxxxxxxxxxxx>
- Re: [PATCH 1/4] ARM: shmobile: sh73a0: fix Z and ZG clock hierarchy
- From: Magnus Damm <magnus.damm@xxxxxxxxx>
- Re: [PATCH 1/4] ARM: shmobile: sh73a0: fix Z and ZG clock hierarchy
- From: Simon Horman <horms@xxxxxxxxxxxx>
- Re: [PATCH v4 2/2] cpufreq: Convert the cpufreq_driver_lock to use the rcu
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- Re: [PATCH] cpufreq: fix sign check of an unsigned variable in cpufreq-cpu0
- From: Mike Turquette <mturquette@xxxxxxxxxx>
- [PATCH] cpufreq: cpufreq-cpu0: use the exact frequency for clk_set_rate()
- From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
- [PATCH/RFC v2 2/2] ARM: shmobile: kzm9g-reference: add CPUFreq support
- From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
- [PATCH/RFC v2 1/2] ARM: shmobile: sh73a0: add support for adjusting CPU frequency
- From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
- [PATCH/RFC v2 0/2] CPUFreq for kzm9g
- From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
- Re: [PATCH v2] cpufreq: highbank: do not initialize array with a loop
- From: Mark Langsdorf <mark.langsdorf@xxxxxxxxxxx>
- Re: [PATCH] cpufreq: fix sign check of an unsigned variable in cpufreq-cpu0
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH] cpufreq: fix sign check of an unsigned variable in cpufreq-cpu0
- From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
- Re: [PATCH v2] cpufreq: highbank: do not initialize array with a loop
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH v2] cpufreq: highbank: do not initialize array with a loop
- From: Emilio López <emilio@xxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: highbank: do not initialize array with a loop
- From: Emilio López <emilio@xxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: highbank: do not initialize array with a loop
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH/RFC 0/4] CPUFreq for kzm9g
- From: Simon Horman <horms@xxxxxxxxxxxx>
- [PATCH] cpufreq: highbank: do not initialize array with a loop
- From: Emilio López <emilio@xxxxxxxxxxxxx>
- Re: [PATCH v4 1/2] cpufreq: Convert the cpufreq_driver_lock to a rwlock
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v4 2/2] cpufreq: Convert the cpufreq_driver_lock to use the rcu
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 1/4] ARM: shmobile: sh73a0: fix Z and ZG clock hierarchy
- From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
- [PATCH/RFC 3/4] ARM: shmobile: sh73a0: run sh73a0_clock_init() only once
- From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
- [PATCH/RFC 2/4] ARM: shmobile: sh73a0: add support for adjusting CPU frequency
- From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
- [PATCH/RFC 0/4] CPUFreq for kzm9g
- From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
- [PATCH 4/4] ARM: shmobile: kzm9g-reference: add CPUFreq support
- From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
- [PATCH v4 2/2] cpufreq: Convert the cpufreq_driver_lock to use the rcu
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- [PATCH v4 1/2] cpufreq: Convert the cpufreq_driver_lock to a rwlock
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- [PATCH v4 0/2] cpufreq: cpufreq_driver_lock is hot on large systems
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- [Bug 54221] ondemand cpufeq governor do not notice Node Manager power limit change
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 54221] New: ondemand cpufeq governor do not notice Node Manager power limit change
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH -next] imx6q-cpufreq: fix return value check in imx6q_cpufreq_probe()
- From: Shawn Guo <shawn.guo@xxxxxxxxxx>
- Re: [PATCH v3 linux-next] cpufreq: ondemand: Calculate gradient of CPU load to early increase frequency
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH v3 linux-next] cpufreq: ondemand: Calculate gradient of CPU load to early increase frequency
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH -next] imx6q-cpufreq: fix return value check in imx6q_cpufreq_probe()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH -next] imx6q-cpufreq: fix return value check in imx6q_cpufreq_probe()
- From: Wei Yongjun <weiyj.lk@xxxxxxxxx>
- Re: [PATCH V2 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V2 3/4] cpufreq: Add Kconfig option to enable/disable have_multiple_policies
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V2 4/4] cpufreq: Get rid of "struct global_attr"
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V2 1/4] cpufreq: Add per policy governor-init/exit infrastructure
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V2 4/4] cpufreq: Get rid of "struct global_attr"
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH V2 2/4] cpufreq: governor: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V2 3/4] cpufreq: Add Kconfig option to enable/disable have_multiple_policies
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH V2 1/4] cpufreq: Add per policy governor-init/exit infrastructure
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V2 4/4] cpufreq: Get rid of "struct global_attr"
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V2 1/4] cpufreq: Add per policy governor-init/exit infrastructure
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH V2 3/4] cpufreq: Add Kconfig option to enable/disable have_multiple_policies
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V2 1/4] cpufreq: Add per policy governor-init/exit infrastructure
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v3 linux-next] cpufreq: ondemand: Calculate gradient of CPU load to early increase frequency
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V2 3/4] cpufreq: Add Kconfig option to enable/disable have_multiple_policies
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH V2 4/4] cpufreq: Get rid of "struct global_attr"
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH V2 1/4] cpufreq: Add per policy governor-init/exit infrastructure
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH v3 2/2] cpufreq: Convert the cpufreq_driver_lock to use the rcu
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- Re: [PATCH v3 linux-next] cpufreq: ondemand: Calculate gradient of CPU load to early increase frequency
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH v2 linux-next] cpufreq: ondemand: Calculate gradient of CPU load to early increase frequency
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v2 linux-next] cpufreq: ondemand: Calculate gradient of CPU load to early increase frequency
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Unable to load the rihgt module for Xeon L5420
- From: Valerio Pachera <sirio81@xxxxxxxxx>
- [Bug 53051] Conservative governor get's sometimes stuck at highest frequency
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH v3 2/2] cpufreq: Convert the cpufreq_driver_lock to use the rcu
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH linux-next] cpufreq: ondemand: Calculate gradient of CPU load to early increase frequency
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH v3 0/2] cpufreq: cpufreq_driver_lock is hot on large systems
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- [PATCH v3 1/2] cpufreq: Convert the cpufreq_driver_lock to a rwlock
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- [PATCH v3 2/2] cpufreq: Convert the cpufreq_driver_lock to use the rcu
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- [PATCH linux-next] cpufreq: ondemand: Calculate gradient of CPU load to early increase frequency
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH v5 2/3] arm: kirkwood: Instantiate cpufreq driver
- From: Jason Cooper <jason@xxxxxxxxxxxxxx>
- [PATCH] cpufreq/intel_pstate: Add kernel command line option disable intel_pstate.
- From: dirk.brandewie@xxxxxxxxx
- Re: [PATCH] cpufreq/intel_pstate: Add kernel command line option disable intel_pstate.
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [PATCH] cpufreq/intel_pstate: Add kernel command line option disable intel_pstate.
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq/intel_pstate: Add kernel command line option disable intel_pstate.
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH] cpufreq/intel_pstate: Add kernel command line option disable intel_pstate.
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq/intel_pstate: Add kernel command line option disable intel_pstate.
- From: Yinghai Lu <yinghai@xxxxxxxxxx>
- [PATCH] cpufreq/intel_pstate: Add kernel command line option disable intel_pstate.
- From: dirk.brandewie@xxxxxxxxx
- Re: [PATCH 0/5] Add P state driver for Intel Core Processors
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH] cpufreq/intel_pstate: Change to disallow module build
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/5] Add P state driver for Intel Core Processors
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [PATCH 0/5] Add P state driver for Intel Core Processors
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [PATCH 0/5] Add P state driver for Intel Core Processors
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 0/5] Add P state driver for Intel Core Processors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/5] Add P state driver for Intel Core Processors
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- [PATCH] cpufreq/intel_pstate: Change to disallow module build
- From: dirk.brandewie@xxxxxxxxx
- [PATCH] cpufreq/intel_pstate: Change to disallow module build
- From: dirk.brandewie@xxxxxxxxx
- Re: [PATCH 0/5] Add P state driver for Intel Core Processors
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [PATCH v2 linux-next 2/2] cpufreq: Convert the cpufreq_driver_lock to use the rcu
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [GIT PULL - cpufreq] Samsung eyxnos cpufreq for v3.9
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- [GIT PULL - cpufreq] Samsung eyxnos cpufreq for v3.9
- From: Kukjin Kim <kgene.kim@xxxxxxxxxxx>
- Re: [PATCH 0/5] Add P state driver for Intel Core Processors
- From: Dave Jones <davej@xxxxxxxxxx>
- Re: [PATCH v2 linux-next 2/2] cpufreq: Convert the cpufreq_driver_lock to use the rcu
- From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
- [Bug 51741] powernow-k8 calls for acpi-cpufreq but doesn’t warn if it’s not available
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH 3/3] dts: Add cpufreq controller node for Exynos5440 SoC
- From: Inderpal Singh <inderpal.singh@xxxxxxxxxx>
- RE: [PATCH v2 linux-next 2/2] cpufreq: Convert the cpufreq_driver_lock to use the rcu
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- Re: [PATCH 3/3] dts: Add cpufreq controller node for Exynos5440 SoC
- From: amit kachhap <amit.kachhap@xxxxxxxxx>
- Re: [PATCH v2 linux-next 2/2] cpufreq: Convert the cpufreq_driver_lock to use the rcu
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- RE: [PATCH v2 linux-next 2/2] cpufreq: Convert the cpufreq_driver_lock to use the rcu
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- Re: [PATCH] cpufreq: dereference cpufreq_driver after check
- From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
- Re: [PATCH] cpufreq: dereference cpufreq_driver after check
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- RE: cpufreq.c:1779 suspicious rcu_dereference_check() usage!
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- [PATCH] cpufreq: dereference cpufreq_driver after check
- From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
- RE: cpufreq.c:1779 suspicious rcu_dereference_check() usage!
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- Re: [cpufreq] WARNING: at kernel/lockdep.c:2739 lockdep_trace_alloc()
- From: Fengguang Wu <fengguang.wu@xxxxxxxxx>
- Re: [cpufreq] WARNING: at kernel/lockdep.c:2739 lockdep_trace_alloc()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V2 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V2 2/4] cpufreq: governor: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V2 3/4] cpufreq: Add Kconfig option to enable/disable have_multiple_policies
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V2 1/4] cpufreq: Add per policy governor-init/exit infrastructure
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V2 4/4] cpufreq: Get rid of "struct global_attr"
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 4/4] cpufreq: governor: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 4/4] cpufreq: governor: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 4/4] cpufreq: governor: Implement per policy instances of governors
- From: Francesco Lavra <francescolavra.fl@xxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 2/2] cpufreq: conservative: Fix typos in comments
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/2] cpufreq: ondemand: Fix typos in comments
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- [Bug 51741] powernow-k8 calls for acpi-cpufreq but doesn’t warn if it’s not available
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 48341] BUG: using smp_processor_id in preemptible powernow_k8
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 48341] BUG: using smp_processor_id in preemptible powernow_k8
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 52941] CPU recognition bug for AMD
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [PATCH 2/2] cpufreq: conservative: Fix typos in comments
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH 1/2] cpufreq: ondemand: Fix typos in comments
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- Re: [PATCH 3/3] dts: Add cpufreq controller node for Exynos5440 SoC
- From: Inderpal Singh <inderpal.singh@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [BUG] cpufreq: sleeping function called from invalid context at kernel/workqueue.c:2811
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: Artem Savkov <artem.savkov@xxxxxxxxx>
- Re: [BUG] cpufreq: sleeping function called from invalid context at kernel/workqueue.c:2811
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/3] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/3] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: amit kachhap <amit.kachhap@xxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: next-20130206 cpufreq - WARN in sysfs_add_one
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/3] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH v2 linux-next 2/2] cpufreq: Convert the cpufreq_driver_lock to use the rcu
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 0/5] Add P state driver for Intel Core Processors
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: Artem Savkov <artem.savkov@xxxxxxxxx>
- Re: next-20130206 cpufreq - WARN in sysfs_add_one
- From: Valdis.Kletnieks@xxxxxx
- Re: [PATCH 2/3] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: amit kachhap <amit.kachhap@xxxxxxxxx>
- Re: [PATCH 2/3] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: amit kachhap <amit.kachhap@xxxxxxxxx>
- Re: [PATCH 3/3] dts: Add cpufreq controller node for Exynos5440 SoC
- From: amit kachhap <amit.kachhap@xxxxxxxxx>
- Re: [PATCH 0/5] Add P state driver for Intel Core Processors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 5/5] cpufreq/x86: Add P-state driver for sandy bridge.
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/5] cpufreq: Retrieve current frequency from scaling drivers with internal governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 3/5] cpufreq: Do not track governor name for scaling drivers with internal governors.
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq Fixes for 3.9
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 2/3] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: Inderpal Singh <inderpal.singh@xxxxxxxxxx>
- Re: [PATCH 1/3] cpufreq: exynos: Remove error return even if no soc found
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/3] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/3] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 3/5] cpufreq: Do not track governor name for scaling drivers with internal governors.
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/5] Add P state driver for Intel Core Processors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/5] cpufreq: Only call cpufreq_out_of_sync() with drivers that implement cpufreq_driver.target()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [BUG] cpufreq: sleeping function called from invalid context at kernel/workqueue.c:2811
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 2/4] cpufreq: Remove unused HOTPLUG_CPU code
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 1/4] cpufreq: governors: Fix WARN_ON() for multi-policy platforms
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 4/4] cpufreq: Fix locking issues
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 3/4] cpufreq: Create a macro for unlock_policy_rwsem{read,write}
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 0/4] CPUFreq Fixes for 3.9
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: next-20130206 cpufreq - WARN in sysfs_add_one
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [BUG] cpufreq: sleeping function called from invalid context at kernel/workqueue.c:2811
- From: Artem Savkov <artem.savkov@xxxxxxxxx>
- Re: [PATCH] cpufreq: exynos: simplify .init() for setting policy->cpus
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/3] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: Inderpal Singh <inderpal.singh@xxxxxxxxxx>
- Re: [PATCH 3/3] dts: Add cpufreq controller node for Exynos5440 SoC
- From: Inderpal Singh <inderpal.singh@xxxxxxxxxx>
- Re: next-20130206 cpufreq - WARN in sysfs_add_one
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: next-20130206 cpufreq - WARN in sysfs_add_one
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: next-20130206 cpufreq - WARN in sysfs_add_one
- From: Valdis.Kletnieks@xxxxxx
- Re: [BUG] cpufreq: sleeping function called from invalid context at kernel/workqueue.c:2811
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: next-20130206 cpufreq - WARN in sysfs_add_one
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [BUG] cpufreq: sleeping function called from invalid context at kernel/workqueue.c:2811
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- [BUG] cpufreq: sleeping function called from invalid context at kernel/workqueue.c:2811
- From: Artem Savkov <artem.savkov@xxxxxxxxx>
- [PATCH 1/3] cpufreq: exynos: Remove error return even if no soc found
- From: Amit Daniel Kachhap <amit.daniel@xxxxxxxxxxx>
- [PATCH 3/3] dts: Add cpufreq controller node for Exynos5440 SoC
- From: Amit Daniel Kachhap <amit.daniel@xxxxxxxxxxx>
- [PATCH 2/3] cpufreq: exynos: Adding cpufreq driver for exynos5440
- From: Amit Daniel Kachhap <amit.daniel@xxxxxxxxxxx>
- next-20130206 cpufreq - WARN in sysfs_add_one
- From: Valdis Kletnieks <Valdis.Kletnieks@xxxxxx>
- [PATCH 1/5] cpufreq: Retrieve current frequency from scaling drivers with internal governors
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 2/5] cpufreq: Only call cpufreq_out_of_sync() for driver that implement cpufreq_driver.target()
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 2/5] cpufreq: Only call cpufreq_out_of_sync() with drivers that implement cpufreq_driver.target()
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 4/5] cpufreq_stats: do not remove sysfs files if frequency table is not present
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 5/5] cpufreq/x86: Add P-state driver for sandy bridge.
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 3/5] cpufreq: Do not track governor name for scaling drivers with internal governors.
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 0/5] Add P state driver for Intel Core Processors
- From: dirk.brandewie@xxxxxxxxx
- Re: [PATCH 5/7] cpufreq: balance out cpufreq_cpu_{get,put} for scaling drivers using setpolicy
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 5/7] cpufreq: balance out cpufreq_cpu_{get,put} for scaling drivers using setpolicy
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [PATCH v2 linux-next 2/2] cpufreq: Convert the cpufreq_driver_lock to use the rcu
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH] cpufreq: ondemand: Replace down_differential tuner with adj_up_threshold
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH v5 1/3] cpufreq: kirkwood: Add a cpufreq driver for Marvell Kirkwood SoCs
- From: Mark Rutland <mark.rutland@xxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Amit Kucheria <amit.kucheria@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v2 linux-next 2/2] cpufreq: Convert the cpufreq_driver_lock to use the rcu
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v5 1/3] cpufreq: kirkwood: Add a cpufreq driver for Marvell Kirkwood SoCs
- From: Shawn Guo <shawn.guo@xxxxxxxxxx>
- Re: [PATCH v5 1/3] cpufreq: kirkwood: Add a cpufreq driver for Marvell Kirkwood SoCs
- From: Andrew Lunn <andrew@xxxxxxx>
- Re: [PATCH v5 1/3] cpufreq: kirkwood: Add a cpufreq driver for Marvell Kirkwood SoCs
- From: Andrew Lunn <andrew@xxxxxxx>
- Re: [PATCH] cpufreq: ondemand: Replace down_differential tuner with adj_up_threshold
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v5 1/3] cpufreq: kirkwood: Add a cpufreq driver for Marvell Kirkwood SoCs
- From: Shawn Guo <shawn.guo@xxxxxxxxxx>
- Re: [PATCH v2 linux-next 2/2] cpufreq: Convert the cpufreq_driver_lock to use the rcu
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v2 linux-next 1/2] cpufreq: Convert the cpufreq_driver_lock to a rwlock
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/7] cpufreq: Retrieve current frequency from scaling drivers with internal governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 5/7] cpufreq: balance out cpufreq_cpu_{get,put} for scaling drivers using setpolicy
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 3/7] cpufreq: Only query drivers that implement cpufreq_driver.target()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/7] cpufreq: Retrieve current frequency from scaling drivers with internal governors
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [PATCH 2/7] cpufreq: Retrieve current frequency from scaling drivers with internal governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 6/7] cpufreq_stats: do not remove sysfs files if frequency table is not present
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/7] cpufreq: Retrieve current frequency from scaling drivers with internal governors
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [PATCH 5/7] cpufreq: balance out cpufreq_cpu_{get,put} for scaling drivers using setpolicy
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [PATCH 3/7] cpufreq: Only query drivers that implement cpufreq_driver.target()
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- [PATCH v2 linux-next 0/2] cpufreq: cpufreq_driver_lock is hot on large systems
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- [PATCH v2 linux-next 2/2] cpufreq: Convert the cpufreq_driver_lock to use the rcu
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- [PATCH v2 linux-next 1/2] cpufreq: Convert the cpufreq_driver_lock to a rwlock
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- Re: [PATCH 5/7] cpufreq: balance out cpufreq_cpu_{get,put} for scaling drivers using setpolicy
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 4/7] cpufreq: Do not track governor name for scaling drivers with internal governors.
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 3/7] cpufreq: Only query drivers that implement cpufreq_driver.target()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/7] cpufreq: Retrieve current frequency from scaling drivers with internal governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/7] cpufreq: Don't remove sysfs link for policy->cpu
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/7] cpufreq: Retrieve current frequency from scaling drivers with internal governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: BUG in bleeding edge c560f3d
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v5 1/3] cpufreq: kirkwood: Add a cpufreq driver for Marvell Kirkwood SoCs
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/2] cpufreq: cpufreq_driver_lock is hot on large systems
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH v5 1/3] cpufreq: kirkwood: Add a cpufreq driver for Marvell Kirkwood SoCs
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: BUG in bleeding edge c560f3d
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- [PATCH] cpufreq: ondemand: Replace down_differential tuner with adj_up_threshold
- From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
- [PATCH v5 1/3] cpufreq: kirkwood: Add a cpufreq driver for Marvell Kirkwood SoCs
- From: Andrew Lunn <andrew@xxxxxxx>
- [PATCH v5 3/3] arm: kirkwood: Enable cpufreq and ondemand on kirkwood_defconfig
- From: Andrew Lunn <andrew@xxxxxxx>
- [PATCH v5 2/3] arm: kirkwood: Instantiate cpufreq driver
- From: Andrew Lunn <andrew@xxxxxxx>
- [PATCH v5 0/3] Kirkwoode cpufreq driver
- From: Andrew Lunn <andrew@xxxxxxx>
- Re: BUG in bleeding edge c560f3d
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Borislav Petkov <bp@xxxxxxxxx>
- RE: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Charles Garcia-Tobin <Charles.Garcia-Tobin@xxxxxxx>
- [PATCH 1/7] cpufreq: Don't remove sysfs link for policy->cpu
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 2/7] cpufreq: Retrieve current frequency from scaling drivers with internal governors
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 3/7] cpufreq: Only query drivers that implement cpufreq_driver.target()
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 7/7] cpufreq/x86: Add P-state driver for sandy bridge.
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 4/7] cpufreq: Do not track governor name for scaling drivers with internal governors.
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 6/7] cpufreq_stats: do not remove sysfs files if frequency table is not present
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 5/7] cpufreq: balance out cpufreq_cpu_{get,put} for scaling drivers using setpolicy
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 0/7] Add P state driver for Intel Core Processors
- From: dirk.brandewie@xxxxxxxxx
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- RE: [PATCH 0/2] cpufreq: cpufreq_driver_lock is hot on large systems
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Borislav Petkov <bp@xxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Borislav Petkov <bp@xxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Borislav Petkov <bp@xxxxxxxxx>
- RE: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Charles Garcia-Tobin <Charles.Garcia-Tobin@xxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Borislav Petkov <bp@xxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Borislav Petkov <bp@xxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Borislav Petkov <bp@xxxxxxxxx>
- Re: [PATCH 0/2] cpufreq: cpufreq_driver_lock is hot on large systems
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: BUG in bleeding edge c560f3d
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 0/2] cpufreq: cpufreq_driver_lock is hot on large systems
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/2] cpufreq: cpufreq_driver_lock is hot on large systems
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Borislav Petkov <bp@xxxxxxxxx>
- Re: [PATCH 0/2] cpufreq: cpufreq_driver_lock is hot on large systems
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/2] cpufreq: Convert the cpufreq_driver_lock to a rwlock
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: BUG in bleeding edge c560f3d
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 5/6] cpufreq: balance out cpufreq_cpu_{get,put} for scaling drivers using setpolicy
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: BUG in bleeding edge c560f3d
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: BUG in bleeding edge c560f3d
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: BUG in bleeding edge c560f3d
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 0/2] cpufreq: cpufreq_driver_lock is hot on large systems
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: BUG in bleeding edge c560f3d
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: BUG in bleeding edge c560f3d
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- [PATCH 1/2] cpufreq: Convert the cpufreq_driver_lock to a rwlock
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- [PATCH 2/2] cpufreq: Convert the cpufreq_driver_lock to use the rcu
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- [PATCH 0/2] cpufreq: cpufreq_driver_lock is hot on large systems
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- BUG in bleeding edge c560f3d
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [PATCH 5/6] cpufreq: balance out cpufreq_cpu_{get,put} for scaling drivers using setpolicy
- From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Borislav Petkov <bp@xxxxxxxxx>
- Re: [PATCH 1/3] cpufreq: TEGRA: Set policy->cpus from driver->init()
- From: Stephen Warren <swarren@xxxxxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Borislav Petkov <bp@xxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Borislav Petkov <bp@xxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Borislav Petkov <bp@xxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v6] cpufreq: add imx6q-cpufreq driver
- From: Shawn Guo <shawn.guo@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Borislav Petkov <bp@xxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Borislav Petkov <bp@xxxxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: exynos: simplify .init() for setting policy->cpus
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v6] cpufreq: add imx6q-cpufreq driver
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- [PATCH 1/4] cpufreq: Don't check cpu_online(policy->cpu)
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 2/4] cpufreq: stats: Get rid of CPUFREQ_STATDEVICE_ATTR
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 3/4] cpufreq: Add per policy governor-init/exit infrastructure
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 4/4] cpufreq: governor: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 0/4] CPUFreq: Implement per policy instances of governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH v6] cpufreq: add imx6q-cpufreq driver
- From: Shawn Guo <shawn.guo@xxxxxxxxxx>
- Re: [PATCH v5] cpufreq: add imx6q-cpufreq driver
- From: Anson Huang <b20788@xxxxxxxxxxxxx>
- Re: [PATCH v5] cpufreq: add imx6q-cpufreq driver
- From: Shawn Guo <shawn.guo@xxxxxxxxxx>
- Re: [PATCH v5] cpufreq: add imx6q-cpufreq driver
- From: Anson Huang <b20788@xxxxxxxxxxxxx>
- [PATCH v5] cpufreq: add imx6q-cpufreq driver
- From: Shawn Guo <shawn.guo@xxxxxxxxxx>
- Re: [PATCH v4 1/3] cpufreq: kirkwood: Add a cpufreq driver for Marvell Kirkwood SoCs
- From: Shawn Guo <shawn.guo@xxxxxxxxxx>
- Re: [PATCH 3/6] cpufreq: Do not track governor name for scaling drivers with internal governors.
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 5/6] cpufreq: balance out cpufreq_cpu_{get,put} for scaling drivers using setpolicy
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 4/6] cpufreq_stats: Do not track policies without associated governors.
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 3/6] cpufreq: Do not track governor name for scaling drivers with internal governors.
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/6] cpufreq: Only query drivers that implement cpufreq_driver.target()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/6] cpufreq: Retrieve current frequency from scaling drivers with internal governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/2] cpufreq: governors: Remove code redundancy between governors
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- [PATCH 1/6] cpufreq: Retrieve current frequency from scaling drivers with internal governors
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 2/6] cpufreq: Only query drivers that implement cpufreq_driver.target()
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 2/6] cpufreq: Only query drivers that implement cpufreq_driver.target()
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 3/6] cpufreq: Do not track governor name for scaling drivers with internal governors.
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 4/6] cpufreq_stats: Do not track policies without associated governors.
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 4/6] cpufreq_stats: Do not track policies without associated governors.
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 6/6] cpufreq/x86: Add P-state driver for sandy bridge.
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 5/6] cpufreq: balance out cpufreq_cpu_{get,put} for scaling drivers using setpolicy
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 3/6] cpufreq: Do not track governor name for scaling drivers with internal governors.
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 1/6] cpufreq: Retrieve current frequency from scaling drivers with internal governors
- From: dirk.brandewie@xxxxxxxxx
- [PATCH 0/6] Add P state driver for Intel Core Processors
- From: dirk.brandewie@xxxxxxxxx
- Re: [PATCH v4 1/3] cpufreq: kirkwood: Add a cpufreq driver for Marvell Kirkwood SoCs
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 43 0/3] Kirkwoode cpufreq driver
- From: Andrew Lunn <andrew@xxxxxxx>
- Re: [PATCH 43 0/3] Kirkwoode cpufreq driver
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 43 0/3] Kirkwoode cpufreq driver
- From: Andrew Lunn <andrew@xxxxxxx>
- [PATCH v4 1/3] cpufreq: kirkwood: Add a cpufreq driver for Marvell Kirkwood SoCs
- From: Andrew Lunn <andrew@xxxxxxx>
- [PATCH v4 2/3] arm: kirkwood: Instantiate cpufreq driver
- From: Andrew Lunn <andrew@xxxxxxx>
- [PATCH v4 3/3] arm: kirkwood: Enable cpufreq and ondemand on kirkwood_defconfig
- From: Andrew Lunn <andrew@xxxxxxx>
- Re: [PATCH 3/3] cpufreq: Remove unnecessary use of policy->shared_type
- From: Santosh Shilimkar <santosh.shilimkar@xxxxxx>
- Re: [PATCH 3/3] cpufreq: Remove unnecessary use of policy->shared_type
- From: Santosh Shilimkar <santosh.shilimkar@xxxxxx>
- Re: [PATCH 3/3] cpufreq: Remove unnecessary use of policy->shared_type
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 3/3] cpufreq: Remove unnecessary use of policy->shared_type
- From: Santosh Shilimkar <santosh.shilimkar@xxxxxx>
- Re: [PATCH 3/3] cpufreq: Remove unnecessary use of policy->shared_type
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 3/3] cpufreq: Remove unnecessary use of policy->shared_type
- From: Santosh Shilimkar <santosh.shilimkar@xxxxxx>
- Re: [PATCH 1/2] cpufreq: governors: Get rid of dbs_data->enable field
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 3/3] cpufreq: Remove unnecessary use of policy->shared_type
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/3] cpufreq: Set all cpus in policy->cpus for single cluster SoCs
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/3] cpufreq: TEGRA: Set policy->cpus from driver->init()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 3/3] cpufreq: Remove unnecessary use of policy->shared_type
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 2/3] cpufreq: Set all cpus in policy->cpus for single cluster SoCs
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 1/3] cpufreq: TEGRA: Set policy->cpus from driver->init()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: governors: Reset tunables only for cpufreq_unregister_governor()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH] cpufreq: governors: Reset tunables only for cpufreq_unregister_governor()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: governors: clean timer init and exit code
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/2] cpufreq: governors: Get rid of dbs_data->enable field
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/2] cpufreq: governors: Remove code redundancy between governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/2] cpufreq: governors: Remove code redundancy between governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/2] cpufreq: governors: Remove code redundancy between governors
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH 2/2] cpufreq: governors: Remove code redundancy between governors
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 1/2] cpufreq: governors: Get rid of dbs_data->enable field
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH 2/2] cpufreq: governors: Remove code redundancy between governors
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH 1/2] cpufreq: governors: Get rid of dbs_data->enable field
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 1/2] cpufreq: governors: Get rid of dbs_data->enable field
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 2/2] cpufreq: governors: Remove code redundancy between governors
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v4] cpufreq: add imx6q-cpufreq driver
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH] cpufreq: governors: clean timer init and exit code
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH] cpufreq: governors: clean timer init and exit code
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH] cpufreq: governors: clean timer init and exit code
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: governors: fix misuse of cdbs.cpu
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH] cpufreq: governors: fix misuse of cdbs.cpu
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH v2] cpufreq: governors: implement generic policy_is_shared
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH v2] cpufreq: governors: implement generic policy_is_shared
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH v7 2/4] cpufreq: ondemand: call dbs_check_cpu only when necessary
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v7 2/4] cpufreq: ondemand: call dbs_check_cpu only when necessary
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH] cpufreq: governors: implement generic policy_is_shared
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: governors: implement generic policy_is_shared
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH v7 2/4] cpufreq: ondemand: call dbs_check_cpu only when necessary
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v7 2/4] cpufreq: ondemand: call dbs_check_cpu only when necessary
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH] cpufreq: governors: implement generic policy_is_shared
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH] cpufreq: governors: implement generic policy_is_shared
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH] cpufreq: SPEAr: Notify all policy->cpus of frequency change
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH] cpufreq: SPEAr: Notify all policy->cpus of frequency change
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] cpufreq: exynos: simplify .init() for setting policy->cpus
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v4] cpufreq: add imx6q-cpufreq driver
- From: Shawn Guo <shawn.guo@xxxxxxxxxx>
- [PATCH] cpufreq: exynos: simplify .init() for setting policy->cpus
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH] cpufreq: Update Documentation for cpus and related_cpus
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v7 1/4] cpufreq: handle SW coordinated CPUs
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- [Bug 52941] CPU recognition bug for AMD
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- cpufreq: cpufreq_driver_lock is quite hot on 512p systems
- From: Nathan Zimmer <nzimmer@xxxxxxx>
- Re: [PATCH v7 3/4] cpufreq: conservative: call dbs_check_cpu only when necessary
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v7 2/4] cpufreq: ondemand: call dbs_check_cpu only when necessary
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v7 1/4] cpufreq: handle SW coordinated CPUs
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH v7 3/4] cpufreq: conservative: call dbs_check_cpu only when necessary
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH v7 1/4] cpufreq: handle SW coordinated CPUs
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v7 2/4] cpufreq: ondemand: call dbs_check_cpu only when necessary
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH v7 1/4] cpufreq: handle SW coordinated CPUs
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH v7 3/4] cpufreq: conservative: call dbs_check_cpu only when necessary
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v7 2/4] cpufreq: ondemand: call dbs_check_cpu only when necessary
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v7 1/4] cpufreq: handle SW coordinated CPUs
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH v3] cpufreq: instantiate cpufreq-cpu0 as a platform_driver
- From: Mark Langsdorf <mark.langsdorf@xxxxxxxxxxx>
- [PATCH v3] cpufreq: instantiate cpufreq-cpu0 as a platform_driver
- From: Shawn Guo <shawn.guo@xxxxxxxxxx>
- [PATCH] cpufreq: governors: clean timer init and exit code
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH v2] cpufreq: instantiate cpufreq-cpu0 as a platform_driver
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH v2] cpufreq: instantiate cpufreq-cpu0 as a platform_driver
- From: Shawn Guo <shawn.guo@xxxxxxxxxx>
- Re: [PATCH v2] cpufreq: instantiate cpufreq-cpu0 as a platform_driver
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 2/5] cpufreq: star/stop cpufreq timers on cpu hotplug
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- [PATCH v7 4/4] cpufreq: ondemand: use all CPUs in update_sampling_rate
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- [PATCH v7 3/4] cpufreq: conservative: call dbs_check_cpu only when necessary
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- [PATCH v7 2/4] cpufreq: ondemand: call dbs_check_cpu only when necessary
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- [PATCH v7 1/4] cpufreq: handle SW coordinated CPUs
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- [PATCH v7 0/5] cpufreq: handle SW coordinated CPUs
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH 1/5] cpufreq: handle SW coordinated CPUs
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH 1/5] cpufreq: handle SW coordinated CPUs
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/5] cpufreq: handle SW coordinated CPUs
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH 2/5] cpufreq: star/stop cpufreq timers on cpu hotplug
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- Re: [PATCH 1/5] cpufreq: handle SW coordinated CPUs
- From: Fabio Baltieri <fabio.baltieri@xxxxxxxxxx>
- RE: [PATCH v2] cpufreq: instantiate cpufreq-cpu0 as a platform_driver
- From: "AnilKumar, Chimata" <anilkumar@xxxxxx>
- Re: [PATCH 1/5] cpufreq: handle SW coordinated CPUs
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 2/5] cpufreq: star/stop cpufreq timers on cpu hotplug
- From: Joseph Lo <josephl@xxxxxxxxxx>
- Re: [PATCH 2/5] cpufreq: star/stop cpufreq timers on cpu hotplug
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V3] cpufreq: Simplify cpufreq_add_dev()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] mailbox: prevent pl320-ipc code from breaking none-AMBA systems
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- RE: [PATCH] mailbox: prevent pl320-ipc code from breaking none-AMBA systems
- From: Mark Langsdorf <mark.langsdorf@xxxxxxxxxxx>
- Re: [PATCH] mailbox: prevent pl320-ipc code from breaking none-AMBA systems
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH 1/2] cpufreq: Set policy->related_cpus to atleast policy->cpus
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH V3] cpufreq: Simplify cpufreq_add_dev()
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- [PATCH] mailbox: prevent pl320-ipc code from breaking none-AMBA systems
- From: Mark Langsdorf <mark.langsdorf@xxxxxxxxxxx>
- [PATCH V3] cpufreq: Simplify cpufreq_add_dev()
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/2] cpufreq: Set policy->related_cpus to atleast policy->cpus
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/2] cpufreq: Set policy->related_cpus to atleast policy->cpus
- From: "Rafael J. Wysocki" <rjw@xxxxxxx>
- Re: [PATCH v2] cpufreq: instantiate cpufreq-cpu0 as a platform_driver
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH 1/2] cpufreq: Set policy->related_cpus to atleast policy->cpus
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 2/2] Revert "cpufreq: Don't use cpu removed during cpufreq_driver_unregister"
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH 1/2] cpufreq: Set policy->related_cpus to atleast policy->cpus
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [Bug 42924] /proc/cpuinfo reports wrong frequency (compared to cpufreq-info)
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 42924] /proc/cpuinfo reports wrong frequency (compared to cpufreq-info)
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH v4] cpufreq: add imx6q-cpufreq driver
- From: Shawn Guo <shawn.guo@xxxxxxxxxx>
- [PATCH v2] cpufreq: instantiate cpufreq-cpu0 as a platform_driver
- From: Shawn Guo <shawn.guo@xxxxxxxxxx>
- [Bug 49881] Missing NULL check of return value of cpufreq_cpu_get() in function cpufreq_add_dev_symlink()
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 49881] Missing NULL check of return value of cpufreq_cpu_get() in function cpufreq_add_dev_symlink()
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 49231] Single CPU bound process results in non-optimal turbo boost configuration
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 49231] Single CPU bound process results in non-optimal turbo boost configuration
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
[Index of Archives]
[Linux Kernel Devel]
[Linux USB Devel]
[Linux SCSI]
[Samba]
[Yosemite News]