linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [next] Odroid XU3 easily over-heats
Date: Mon, 15 Feb 2016 10:58:43 +0530	[thread overview]
Message-ID: <20160215052843.GA6334@vireshk-i7> (raw)
In-Reply-To: <56C01963.3080106@gmail.com>

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

  reply	other threads:[~2016-02-15  5:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14  6:06 [next] Odroid XU3 easily over-heats Krzysztof Kozlowski
2016-02-15  5:28 ` Viresh Kumar [this message]
2016-02-15  6:36   ` Krzysztof Kozlowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160215052843.GA6334@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).