linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: Doug Anderson <dianders@chromium.org>
Cc: Chander Kashyap <k.chander@samsung.com>,
	Kukjin Kim <kgene.kim@samsung.com>,
	Nicolas Pitre <nicolas.pitre@linaro.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
	Kevin Hilman <khilman@linaro.org>,
	Andrew Bresticker <abrestic@chromium.org>,
	Inderpal Singh <inderpal.s@samsung.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Chander Kashyap <chander.kashyap@linaro.org>,
	"olof@lixom.net" <olof@lixom.net>,
	Tushar Behera <trblinux@gmail.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Thomas Abraham <thomas.ab@samsung.com>,
	Abhilash Kesavan <a.kesavan@samsung.com>,
	Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
	"linux-samsung-soc@vger.kernel.org" 
	<linux-samsung-soc@vger.kernel.org>
Subject: Re: [PATCH] ARM: EXYNOS: mcpm: Don't rely on firmware's secondary_cpu_start
Date: Thu, 12 Jun 2014 00:28:15 +0900	[thread overview]
Message-ID: <5398758F.4080306@samsung.com> (raw)
In-Reply-To: <CAD=FV=ULFx0GPp_mnEfouZF+m4h_RYE6WQu48N0WbFWrFv8-BA@mail.gmail.com>

On 06/12/14 00:19, Doug Anderson wrote:
> Chander,
>
> On Tue, Jun 10, 2014 at 9:52 PM, Chander Kashyap<k.chander@samsung.com>  wrote:
>> Hi Doug,
>>
>> On Tue, Jun 10, 2014 at 9:19 PM, Nicolas Pitre<nicolas.pitre@linaro.org>  wrote:
>>> 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).
>>>>
>>
>> No Its not plain WFI.
>>
>> All cores in Exynos5420 can be powered off independently.
>> This functionality has been tested.
>>
>> Below is the link for the posted patches.
>>
>> https://lkml.org/lkml/2014/6/10/194
>>
>> And as Nicolas wrote, these patches need MCPM for that.
>
> Most excellent!  I should have been more clear that I only knew about
> how CPUidle worked in our local production kernel.  There I'm pretty
> sure CPUidle is just WFI/WFE.  If you've got patches to do better then
> that's great!
>
> ...can you confirm that my patch doesn't interfere with your improved
> CPUidle?  It's been Acked by Nicolas (thanks!) so I'd imagine it will
> land shortly.  Kukjin: I assume you'll be taking this?
>
Sure, I will ;-)

Thanks,
Kukjin

  reply	other threads:[~2014-06-11 15:28 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
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 [this message]
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=5398758F.4080306@samsung.com \
    --to=kgene.kim@samsung.com \
    --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=k.chander@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=nicolas.pitre@linaro.org \
    --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).