Re: [PATCH v3 2/6] thermal: Add generic cpufreq cooling implementation

On Tue, 8 May 2012 21:48:14 +0530 Amit Daniel Kachhap wrote: > This patch adds support for generic cpu thermal cooling low level > implementations using frequency scaling up/down based on the registration > parameters. Different cpu related cooling devices can be registered by the > user and the

Re: [PATCH v3 5/6] thermal: exynos: Register the tmu sensor with the kernel thermal layer

On Tue, 8 May 2012 21:48:17 +0530 Amit Daniel Kachhap wrote: > This code added creates a link between temperature sensors, linux thermal > framework and cooling devices for samsung exynos platform. This layer > monitors the temperature from the sensor and informs the generic thermal > layer to t

Re: [PATCH v3 6/6] ARM: exynos: Add thermal sensor driver platform data support

On Tue, 8 May 2012 21:48:18 +0530 Amit Daniel Kachhap wrote: > This patch adds necessary default platform data support needed for TMU driver. > This dt/non-dt values are tested for origen exynos4210 and smdk exynos5250 > platforms. > > > ... > > --- a/drivers/thermal/exynos_thermal.c > +++ b/d

Re: [PATCH v3 3/6] hwmon: exynos4: Move thermal sensor driver to driver/thermal directory

On Tue, 8 May 2012 21:48:15 +0530 Amit Daniel Kachhap wrote: > This movement is needed because the hwmon entries and corresponding > sysfs interface is a duplicate of utilities already provided by > driver/thermal/thermal_sys.c. The goal is to place it in thermal folder > and add necessary funct

Re: [PATCH v3 0/6] thermal: exynos: Add kernel thermal support for exynos platform

On Tue, 8 May 2012 21:48:12 +0530 Amit Daniel Kachhap wrote: > This patchset introduces a new generic cooling device based on cpufreq that > can be used on non-ACPI platforms. As a proof of concept, we have drivers for > the following platforms using this mechanism now: > > * TI OMAP (git://gi

Re: [RFC PATCH] hrtimers: system-wide and per-task hrtimer slacks

On Mon, 20 Feb 2012 11:49:32 +0400 Dmitry Antipov wrote: > This patch proposes a system-wide sysctl-aware default for the > high-resolution timer slack value, which may be changed from 0 > to HRTIMER_MAX_SLACK nanoseconds. Default system-wide and per-task > values are HRTIMER_DEFAULT_SLACK. Per-t

Re: [RFC PATCH] module: debugging check for runaway kthreads

On Tue, 28 Feb 2012 13:04:23 +0400 Dmitry Antipov wrote: > Debugging option CONFIG_MODULE_KTHREAD_CHECK provides a way to check > whether all kernel threads created by the module and have used module > code as a thread worker function are really exited when the module is > unloaded. The following