From: Nicolas Pitre <nicolas.pitre@linaro.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Chander Kashyap <chander.kashyap@linaro.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Kukjin Kim <kgene.kim@samsung.com>,
Abhilash Kesavan <a.kesavan@samsung.com>,
Andrew Bresticker <abrestic@chromium.org>,
Inderpal Singh <inderpal.s@samsung.com>,
Thomas Abraham <thomas.ab@samsung.com>,
"olof@lixom.net" <olof@lixom.net>,
Tushar Behera <trblinux@gmail.com>,
Kevin Hilman <khilman@linaro.org>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: EXYNOS: mcpm: Don't rely on firmware's secondary_cpu_start
Date: Tue, 10 Jun 2014 11:49:27 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1406101146140.25775@knanqh.ubzr> (raw)
In-Reply-To: <CAD=FV=V5_RRNkgA7Rk7XbQw9m1qh6-RJA8arW7ZRU=QbWAPa+w@mail.gmail.com>
On Tue, 10 Jun 2014, Doug Anderson wrote:
> My S-state knowledge is not strong, but I believe that Lorenzo's
> questions matter if we're using S2 for CPUidle (where we actually turn
> off power and hot unplug CPUs) but not when we're using S1 for CPUidle
> (where we just enter WFI/WFE).
>
> I believe that in ChromeOS we use S1 CPUidle and that it works fine.
> We've never implemented S2 that I'm aware of.
You'll have to rely on MCPM for that. That's probably why it hasn't
been implemented before.
Nicolas
next prev parent reply other threads:[~2014-06-10 15:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 21:43 [PATCH] ARM: EXYNOS: mcpm: Don't rely on firmware's secondary_cpu_start Doug Anderson
2014-06-06 22:35 ` Nicolas Pitre
2014-06-06 22:43 ` Doug Anderson
2014-06-06 22:46 ` Andrew Bresticker
2014-06-06 23:14 ` [PATCH v2] " Doug Anderson
2014-06-07 1:34 ` Nicolas Pitre
2014-06-09 18:09 ` Kevin Hilman
2014-06-09 20:05 ` Andrew Bresticker
2014-06-09 20:22 ` Nicolas Pitre
2014-06-09 20:35 ` Kevin Hilman
2014-06-09 20:55 ` Nicolas Pitre
2014-06-16 18:37 ` Doug Anderson
2014-06-16 18:47 ` Nicolas Pitre
2014-06-07 18:12 ` [PATCH] " Lorenzo Pieralisi
2014-06-09 17:03 ` Doug Anderson
2014-06-09 22:38 ` Lorenzo Pieralisi
2014-06-10 8:12 ` Chander Kashyap
2014-06-10 15:21 ` Doug Anderson
2014-06-10 15:49 ` Nicolas Pitre [this message]
2014-06-11 4:52 ` Chander Kashyap
2014-06-11 10:13 ` Lorenzo Pieralisi
2014-06-11 12:14 ` Chander Kashyap
2014-06-11 13:15 ` Lorenzo Pieralisi
2014-06-11 13:29 ` Chander Kashyap
2014-06-11 13:34 ` Abhilash Kesavan
2014-06-11 15:19 ` Doug Anderson
2014-06-11 15:28 ` Kukjin Kim
2014-06-13 11:54 ` Chander Kashyap
2014-06-13 13:29 ` Nicolas Pitre
2014-06-13 15:10 ` Doug Anderson
2014-06-16 7:40 ` Chander Kashyap
2014-06-16 18:35 ` Doug Anderson
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=alpine.LFD.2.11.1406101146140.25775@knanqh.ubzr \
--to=nicolas.pitre@linaro.org \
--cc=a.kesavan@samsung.com \
--cc=abrestic@chromium.org \
--cc=chander.kashyap@linaro.org \
--cc=dianders@chromium.org \
--cc=inderpal.s@samsung.com \
--cc=javier.martinez@collabora.co.uk \
--cc=kgene.kim@samsung.com \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lorenzo.pieralisi@arm.com \
--cc=olof@lixom.net \
--cc=thomas.ab@samsung.com \
--cc=trblinux@gmail.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).