From: Nishanth Menon <nm@ti.com>
To: Tomasz Figa <tomasz.figa@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
Thomas Abraham <ta.omasab@gmail.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"kgene.kim@samsung.com" <kgene.kim@samsung.com>,
"t.figa@samsung.com" <t.figa@samsung.com>,
"l.majewski@samsung.com" <l.majewski@samsung.com>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <Pawel.Moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH v6 2/2] Documentation: devicetree: Add boost-frequency binding to list boost mode frequency
Date: Fri, 30 May 2014 16:01:17 -0500 [thread overview]
Message-ID: <5388F19D.8070303@ti.com> (raw)
In-Reply-To: <5388ED87.1090209@gmail.com>
On 05/30/2014 03:43 PM, Tomasz Figa wrote:
[...]
> OK, so you add overclocked frequencies to operating-points property,
> boost-frequency property, build a dtb, use it with a kernel that doesn't
> support boost-frequency and nicely overheat (and likely destroy) your
> board. I don't think this makes too much sense, sorry.
Yes, that is unfortunately true as well :( Sigh.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2014-05-30 21:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 9:01 [PATCH v6 0/2] cpufreq: opp: Add device tree based lookup of boost mode frequency Thomas Abraham
2014-05-30 9:01 ` [PATCH v6 1/2] cpufreq / OPP: Allow boost frequency to be looked up from device tree Thomas Abraham
2014-05-30 9:01 ` [PATCH v6 2/2] Documentation: devicetree: Add boost-frequency binding to list boost mode frequency Thomas Abraham
2014-05-30 13:08 ` Mark Rutland
2014-05-30 18:05 ` Thomas Abraham
2014-05-30 18:15 ` Tomasz Figa
2014-05-30 18:33 ` Thomas Abraham
2014-05-30 18:35 ` Tomasz Figa
2014-05-30 18:38 ` Sudeep Holla
2014-05-30 18:41 ` Tomasz Figa
2014-05-30 18:48 ` Sudeep Holla
2014-05-30 18:55 ` Mark Rutland
2014-05-30 19:50 ` Nishanth Menon
2014-05-30 20:02 ` Tomasz Figa
2014-05-30 20:13 ` Nishanth Menon
2014-05-30 20:19 ` Tomasz Figa
2014-05-30 20:33 ` Nishanth Menon
2014-05-30 20:43 ` Tomasz Figa
2014-05-30 21:01 ` Nishanth Menon [this message]
2014-05-30 20:45 ` Rob Herring
2014-05-30 20:59 ` Nishanth Menon
2014-05-30 12:19 ` [PATCH v6 0/2] cpufreq: opp: Add device tree based lookup of " Rafael J. Wysocki
2014-05-30 14:47 ` Rafael J. Wysocki
2014-05-30 18:07 ` Thomas Abraham
2014-05-30 21:17 ` Rafael J. Wysocki
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=5388F19D.8070303@ti.com \
--to=nm@ti.com \
--cc=Pawel.Moll@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kgene.kim@samsung.com \
--cc=l.majewski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=t.figa@samsung.com \
--cc=ta.omasab@gmail.com \
--cc=tomasz.figa@gmail.com \
--cc=viresh.kumar@linaro.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).