linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v9 0/4] Consolidating GIC per-cpu interrupts
Date: Mon, 01 Aug 2011 09:20:55 +0100	[thread overview]
Message-ID: <4E3661E7.2000003@arm.com> (raw)
In-Reply-To: <4E3102F0.4030705@codeaurora.org>

On 28/07/11 07:34, Stephen Boyd wrote:
> On 07/21/2011 09:57 AM, Marc Zyngier wrote:
>> The current GIC per-cpu interrupts (aka PPIs) suffer from a number of
>> problems:
>>
> [snip]
>>
>> Patches against next-20110721, tested on PB11MP. As this patch series
>> is quite different from the previous one, I've dropped all previous
>> acks from platform maintainers.
> 
> I tried this out the other day and it didn't work. The setup_irq() calls
> in msm timer code fails and then we calibrate delay forever. I haven't
> looked further.

Ah, of course. Need to do a gic_request_ppi() on CPU0's timer instead of
request_irq(), but only on msm8x60/msm8960. Not very nice.

I'll update the patches and repost them later today.

Cheers,

	M.
-- 
Jazz is not dead. It just smells funny...

      reply	other threads:[~2011-08-01  8:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-21 16:57 [RFC PATCH v9 0/4] Consolidating GIC per-cpu interrupts Marc Zyngier
2011-07-21 16:57 ` [RFC PATCH v9 1/4] ARM: gic: consolidate PPI handling Marc Zyngier
2011-07-22  9:42   ` Russell King - ARM Linux
2011-07-22 10:01     ` Marc Zyngier
2011-07-21 16:57 ` [RFC PATCH v9 2/4] ARM: gic: Add PPI registration interface Marc Zyngier
2011-07-22  0:21   ` Jeff Ohlstein
2011-07-22  9:30     ` Marc Zyngier
2011-07-21 16:57 ` [RFC PATCH v9 3/4] ARM: local timers: drop local_timer_ack() Marc Zyngier
2011-07-21 16:57 ` [RFC PATCH v9 4/4] ARM: gic: add compute_irqnr macro for exynos4 Marc Zyngier
2011-07-28  6:34 ` [RFC PATCH v9 0/4] Consolidating GIC per-cpu interrupts Stephen Boyd
2011-08-01  8:20   ` Marc Zyngier [this message]

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=4E3661E7.2000003@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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).