From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752242AbcBOF2y (ORCPT <rfc822;w@1wt.eu>);
	Mon, 15 Feb 2016 00:28:54 -0500
Received: from mail-pf0-f179.google.com ([209.85.192.179]:33359 "EHLO
	mail-pf0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751956AbcBOF2v (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 15 Feb 2016 00:28:51 -0500
Date: Mon, 15 Feb 2016 10:58:43 +0530
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Krzysztof Kozlowski <k.kozlowski.k@gmail.com>
Cc: Lukasz Majewski <l.majewski@samsung.com>,
        Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
        "Rafael J. Wysocki" <rjw@rjwysocki.net>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Zhang Rui <rui.zhang@intel.com>,
        Eduardo Valentin <edubezval@gmail.com>,
        linux-arm-kernel@lists.infradead.org,
        linux-samsung-soc@vger.kernel.org,
        Javier Martinez Canillas <javier@osg.samsung.com>,
        Kukjin Kim <kgene@kernel.org>,
        Krzysztof Kozlowski <k.kozlowski@samsung.com>
Subject: Re: [next] Odroid XU3 easily over-heats
Message-ID: <20160215052843.GA6334@vireshk-i7>
References: <56C01963.3080106@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <56C01963.3080106@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 14-02-16, 15:06, Krzysztof Kozlowski wrote:
> Hi all,
> 
> With recent addition of cpufreq-dt support to Exynos5422
> it is very easy to over-heat the Odroid XU3 leading to critical shutdown:

How were OPPs passed earlier? I failed to see them in kernel somehow.
You must have been using opp-v1 earlier, right?

You used boost-freqs then? You used cpufreq as a cooling device then?

> What about cpufreq as cooling device? Probably that part
> is missing now, right?

Maybe, how was that earlier though ?

-- 
viresh