From: Nishanth Menon <nm@ti.com>
To: Keerthy <a0393675@ti.com>, Tony Lindgren <tony@atomide.com>
Cc: Eduardo Valentin <edubezval@gmail.com>,
Keerthy <j-keerthy@ti.com>,
Dmitry Lifshitz <lifshitz@compulab.co.il>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
lkml <linux-kernel@vger.kernel.org>,
dt list <devicetree@vger.kernel.org>,
linux-omap <linux-omap@vger.kernel.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Kumar Gala <galak@codeaurora.org>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] arm: dts: AM57XX: Correct the thermal thresholds
Date: Mon, 15 Feb 2016 11:25:38 -0600 [thread overview]
Message-ID: <56C20A12.8080305@ti.com> (raw)
In-Reply-To: <56C1F92A.1020803@ti.com>
On 02/15/2016 10:13 AM, Keerthy wrote:
[...]
>>
>> This data is in the AM572x datasheet:
>> http://www.ti.com/lit/ds/symlink/am5728.pdf
>>
>> Table 5-3 in the current version contains the maximum junction
>> temperatures.
>>
>> this indicates that there are "Commercial" and "extended" -> we may
>> need to introduce just 2 dtsis -> am57xx-commercial and
>> am57xx-extended and reuse those based on the part on the board. just a
>> suggestion..
>
> Or use the minimum of the 2 to be on the safer side if we have to deal
> with one dtsi?
Why would we want to throttle earlier on customer platforms or other
boards using extended? at the very least -> if all upstream boards
have only commercial grade, then just introduce
am57xx-commercial-thermal.dtsi ..
--
Regards,
Nishanth Menon
prev parent reply other threads:[~2016-02-15 17:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 9:45 [PATCH] arm: dts: AM57XX: Correct the thermal thresholds Keerthy
2016-02-09 22:09 ` Eduardo Valentin
2016-02-09 22:16 ` Nishanth Menon
[not found] ` <56BA6530.4030102-l0cyMroinI0@public.gmane.org>
2016-02-12 22:23 ` Tony Lindgren
2016-02-12 22:30 ` Nishanth Menon
[not found] ` <CAGo_u6r8-LJBWWrew0fV50Q+JnCxDj9PD57+9NoDm5TqCWL=jw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-12 22:41 ` Tony Lindgren
2016-02-15 4:27 ` Keerthy
2016-02-15 15:49 ` Nishanth Menon
2016-02-15 16:13 ` Keerthy
2016-02-15 17:25 ` Nishanth Menon [this message]
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=56C20A12.8080305@ti.com \
--to=nm@ti.com \
--cc=a0393675@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=j-keerthy@ti.com \
--cc=lifshitz@compulab.co.il \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=tony@atomide.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 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).