linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: A clockevent IRQ delivery question
Date: Fri, 20 Jun 2014 17:24:15 +0200	[thread overview]
Message-ID: <53A4521F.2070309@linaro.org> (raw)
In-Reply-To: <CAJgR-Bj+tgCpKTT7FxM-1JMvN7CKUgpaikfbXPQx5ep6+7W2mA@mail.gmail.com>

On 06/20/2014 05:18 PM, Jon Loeliger wrote:
>>
>> Hi Jon,
>
> Hi Daniel,
>
>> you can have a look at the exynos_mct driver which has similar design.
>
> OK, I'll give that a once-over!
>
> So yeah, it is pretty clearly doing what I was (slowly) deducing: PPIs are
> getting percpu stuff, and SPI are all getting just this
> smp_processor_id() stuff.
>
>> There was a notifier for cpu bootup but Thomas added a force affinity api,
>> so even if the cpu is not in the online mask, the irq is correctly set
>> (commit 30ccf03b).
>
> Ah, I see.  I'll track that commit down.  Thanks.

You are welcome. Let me know if that helped you.

Thanks
   -- Daniel

>> By the way, did you try to use the A9 local timers (twd) ?
>
> Not yet.  I hit the global timer just to get my port going.  I needed to
> implement and verify our timer block.  But I can give the TWD a
> run as well!
>
> Thanks!
> jdl
>


-- 
  <http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

      parent reply	other threads:[~2014-06-20 15:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19 16:17 A clockevent IRQ delivery question Jon Loeliger
2014-06-20  5:51 ` Viresh Kumar
2014-06-20 14:24   ` Jon Loeliger
2014-06-20 14:35 ` Daniel Lezcano
2014-06-20 15:18   ` Jon Loeliger
2014-06-20 15:23     ` Russell King - ARM Linux
2014-06-20 15:31       ` Jon Loeliger
2014-06-21 22:44         ` Jon Loeliger
2014-06-21 23:11           ` Russell King - ARM Linux
2014-06-20 15:24     ` Daniel Lezcano [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=53A4521F.2070309@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --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).