From: Viresh Kumar <viresh.kumar@linaro.org>
To: Amit Kucheria <amit.kucheria@linaro.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Ram Chandrasekar <rkumbako@codeaurora.org>,
DTML <devicetree@vger.kernel.org>,
Lina Iyer <ilina@codeaurora.org>, Zhang Rui <rui.zhang@intel.com>,
Eduardo Valentin <edubezval@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Linux PM list <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] thermal: of: Allow selection of thermal governor in DT
Date: Thu, 8 Mar 2018 11:12:21 +0530 [thread overview]
Message-ID: <20180308054221.GJ6842@vireshk-i7> (raw)
In-Reply-To: <CAP245DWAnYqbKJ_+NMqYvP9suwgmmkZ6twSBfAD64FxqztgnuA@mail.gmail.com>
On 08-03-18, 11:05, Amit Kucheria wrote:
> Interestingly enough, there are some patches that make the thermal
> framework start earlier to deal with boot-time thermal issues. I
> expect to post them soon. :-) These are required, for example, if the
> device goes into a reboot loop - the device might not even make it to
> the point in userspace where the governors are setup. In such a loop,
> the temperature constantly keeps increasing.
>
> I was refering to the 'make defconfig' out-of-box experience that
> makes the majority of developer boards/devices out there stable to
> work on. I can't do that today.
Fair enough, but I am still not sure if we should put something that defines our
thermal policy into DT which should describe hardware.
--
viresh
next prev parent reply other threads:[~2018-03-08 5:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1520274879.git.amit.kucheria@linaro.org>
2018-03-05 18:36 ` [PATCH] thermal: of: Allow selection of thermal governor in DT Amit Kucheria
2018-03-05 20:08 ` Rob Herring
2018-03-06 5:38 ` Amit Kucheria
2018-03-05 21:11 ` Daniel Lezcano
2018-03-06 5:48 ` Amit Kucheria
2018-03-06 15:43 ` Daniel Lezcano
2018-03-06 12:32 ` Sudeep Holla
2018-03-07 10:59 ` Amit Kucheria
2018-03-08 4:49 ` Viresh Kumar
2018-03-08 5:35 ` Amit Kucheria
2018-03-08 5:42 ` Viresh Kumar [this message]
2018-03-08 12:41 ` Sudeep Holla
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=20180308054221.GJ6842@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=amit.kucheria@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=ilina@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rkumbako@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=sudeep.holla@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.