From: Rob Herring <robh@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Amit Kucheria <amit.kucheria@linaro.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] DT: bindings: Add cooling cells for idle states
Date: Wed, 8 Jan 2020 08:03:33 -0600 [thread overview]
Message-ID: <20200108140333.GA12276@bogus> (raw)
In-Reply-To: <20191219221932.15930-1-daniel.lezcano@linaro.org>
On Thu, Dec 19, 2019 at 11:19:27PM +0100, Daniel Lezcano wrote:
> Add DT documentation to add an idle state as a cooling device. The CPU
> is actually the cooling device but the definition is already used by
> frequency capping. As we need to make cpufreq capping and idle
> injection to co-exist together on the system in order to mitigate at
> different trip points, the CPU can not be used as the cooling device
> for idle injection. The idle state can be seen as an hardware feature
> and therefore as a component for the passive mitigation.
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> ---
> Documentation/devicetree/bindings/arm/idle-states.txt | 11 +++++++++++
> 1 file changed, 11 insertions(+)
This is now a schema in my tree. Can you rebase on that and I'll pick up
the binding change.
Rob
next prev parent reply other threads:[~2020-01-08 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 22:19 [PATCH 1/2] DT: bindings: Add cooling cells for idle states Daniel Lezcano
2020-01-08 14:03 ` Rob Herring [this message]
2020-01-11 17:32 ` Daniel Lezcano
2020-01-13 16:16 ` Rob Herring
2020-01-13 17:52 ` Daniel Lezcano
2020-01-27 18:29 ` Daniel Lezcano
2020-01-28 0:21 ` Rob Herring
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=20200108140333.GA12276@bogus \
--to=robh@kernel.org \
--cc=amit.kucheria@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.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).