Hi Viresh,
On 21 January 2015 at 15:17, Lukasz Majewski l.majew...@samsung.com
wrote:
In previous versions I've only checked for cpu 0.
If you think that it is enough to explicitly check only for cpu 0
and forget about above fail safe code (when. e.g. CPU3 has defined
cooling-cells),
Hi Eduardo,
On Mon, Jan 19, 2015 at 12:20:51PM +0100, Lukasz Majewski wrote:
Up till now exynos_tmu_data.c was used for storing CPU cooling
configuration data. Now the Exynos thermal core code uses device
tree to get this data. For this purpose generic thermal code for
configuring CPU
Hi Viresh,
Up till now exynos_tmu_data.c was used for storing CPU cooling
configuration data. Now the Exynos thermal core code uses device tree
to get this data. For this purpose generic thermal code for
configuring CPU cooling was used.
Signed-off-by: Lukasz Majewski
Hi Viresh,
On 21 January 2015 at 14:03, Lukasz Majewski l.majew...@samsung.com
wrote:
diff --git a/drivers/cpufreq/exynos-cpufreq.c
static int exynos_cpufreq_probe(struct platform_device *pdev)
{
+ struct device_node *cpus, *np;
int ret = -EINVAL;
exynos_info =
On 21 January 2015 at 14:03, Lukasz Majewski l.majew...@samsung.com wrote:
diff --git a/drivers/cpufreq/exynos-cpufreq.c
static int exynos_cpufreq_probe(struct platform_device *pdev)
{
+ struct device_node *cpus, *np;
int ret = -EINVAL;
exynos_info =
On 21 January 2015 at 15:17, Lukasz Majewski l.majew...@samsung.com wrote:
In previous versions I've only checked for cpu 0.
If you think that it is enough to explicitly check only for cpu 0 and
forget about above fail safe code (when. e.g. CPU3 has defined
cooling-cells), then I'm fine with
On Mon, Jan 19, 2015 at 12:20:51PM +0100, Lukasz Majewski wrote:
Up till now exynos_tmu_data.c was used for storing CPU cooling configuration
data. Now the Exynos thermal core code uses device tree to get this data.
For this purpose generic thermal code for configuring CPU cooling was
used.
