public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rickard Andersson <rickard.andersson@stericsson.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
	"john.stultz@linaro.org" <john.stultz@linaro.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
	"jacob.jun.pan@linux.intel.com" <jacob.jun.pan@linux.intel.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
	"patches@linaro.org" <patches@linaro.org>,
	Linus WALLEIJ <linus.walleij@stericsson.com>
Subject: Re: [PATCH 0/4] time: dynamic irq affinity
Date: Mon, 11 Mar 2013 10:28:29 +0100	[thread overview]
Message-ID: <513DA3BD.4070003@stericsson.com> (raw)
In-Reply-To: <513DA009.9080601@ti.com>

On 03/11/2013 10:12 AM, Santosh Shilimkar wrote:
> On Monday 11 March 2013 02:10 PM, Daniel Lezcano wrote:
>> On 03/11/2013 04:24 AM, Santosh Shilimkar wrote:
>>> On Sunday 10 March 2013 11:52 PM, Daniel Lezcano wrote:
>> [ ... ]
>>
>>>> I don't think it is the case for all the ARM platforms, at least we
>>>> tested it on vexpress TC2 and u8500, and the number of IPI were reduced
>>>> very significantly increasing the idle time for cpu0. TC2 will need
>>>> another optimization on another area for the idle wake up to gain real
>>>> improvements.
>>>>
>>> You are missing my point. TC2 can be an exception since the SGI can wakeup
>>> CPUs even from low power states where local timer's are stalled. Is that
>>> the case with U8500 ?
>> Well, the cpuidle driver is not going into a deep idle state to check
>> this out.
>>
>> AFAICT this board has a specific firmware with the PRCMU (a device
>> managing the power on the board) and it replaces the GIC when going to
>> deep idle state, especially by reconnecting the GIC to the A9 cores
>> automatically when an interrupt occurs.
>>
> But most likely it will be limited to peripheral interrupts. SGI's
> are per-cpu irq's so you need to check that part.
>
In the U8500 case, when the first CPU is woken up it will work ok for 
that CPU to send an IPI to the other CPU.

BR
Rickard

  reply	other threads:[~2013-03-11  9:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26 22:17 [PATCH 0/4] time: dynamic irq affinity Daniel Lezcano
2013-02-26 22:17 ` [PATCH 1/4] time : pass broadcast parameter Daniel Lezcano
2013-02-27  5:09   ` Santosh Shilimkar
2013-02-26 22:17 ` [PATCH 2/4] time : set broadcast irq affinity Daniel Lezcano
2013-02-27  5:33   ` Santosh Shilimkar
2013-02-26 22:17 ` [PATCH 3/4] ARM: nomadik: add dynamic irq flag to the timer Daniel Lezcano
2013-03-01  1:13   ` Linus Walleij
2013-03-01  8:56     ` Vincent Guittot
2013-03-01 13:28       ` Rickard Andersson
2013-02-26 22:17 ` [PATCH 4/4] ARM: timer-sp: Set dynamic irq affinity Daniel Lezcano
2013-02-27  4:56   ` Santosh Shilimkar
2013-02-27  4:59     ` Viresh Kumar
2013-02-27  5:04       ` Santosh Shilimkar
2013-02-27  6:00 ` [PATCH 0/4] time: " Santosh Shilimkar
2013-02-27 10:47   ` Russell King - ARM Linux
2013-02-27 22:00     ` Thomas Gleixner
2013-03-10 17:33 ` Santosh Shilimkar
2013-03-10 18:22   ` Daniel Lezcano
2013-03-11  3:24     ` Santosh Shilimkar
2013-03-11  8:40       ` Daniel Lezcano
2013-03-11  9:12         ` Santosh Shilimkar
2013-03-11  9:28           ` Rickard Andersson [this message]
2013-03-11 10:29             ` Santosh Shilimkar

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=513DA3BD.4070003@stericsson.com \
    --to=rickard.andersson@stericsson.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=john.stultz@linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=patches@linaro.org \
    --cc=santosh.shilimkar@ti.com \
    --cc=tglx@linutronix.de \
    --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