linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/7] ARM: pxa: add devicetree code for irq handling
Date: Mon, 30 Jul 2012 10:34:04 +0200	[thread overview]
Message-ID: <501646FC.60900@gmail.com> (raw)
In-Reply-To: <201207300831.32988.arnd@arndb.de>

On 30.07.2012 10:31, Arnd Bergmann wrote:
> On Sunday 29 July 2012, Daniel Mack wrote:
>> Hmm, PXA25x (which does not feature IRQ priorities) shares a fair amount
>> of peripherals with other PXA series (which do have support for that). I
>> would much like to reflect that fact by inherhiting device nodes from
>> one dtsi to the other. Hence, if at all, we would need to have two cells
>> always, and just ignore the second argument on PXA25x.
> 
> But that can only work if the interrupt numbers are identical between PXA25x
> and the other SoCs. Are they?

Yes.

>> And I also wonder whether using the second spec value for a priority
>> wouldn't be somehow abusive? Isn't that considered to denote the trigger
>> flags in contexts of interrupt controllers? At least, that is what
>> irq_domain_xlate_twocell() assumes.
> 
> You would not use irq_domain_xlate_twocell in that scenario but provide your
> own, which is ok. Interpreting the second cell as the trigger flags is just
> a convenient default because it's the most common use for that.

I see. Don't know how much sense it makes to have that detail
configurable though. Haojian? And I think we can still change that
detail later.


Daniel

  reply	other threads:[~2012-07-30  8:34 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 19:16 [PATCH v2 0/7] Assorted PXA3xx DT patches Daniel Mack
2012-07-26 19:16 ` [PATCH v2 1/7] RTC: add DT bindings to pxa-rtc Daniel Mack
2012-07-26 19:16 ` [PATCH v2 2/7] MMC: pxa-mci: add DT bindings Daniel Mack
2012-07-26 19:16 ` [PATCH v2 3/7] MTD: pxa3xx-nand: add devicetree bindings Daniel Mack
2012-07-26 19:16 ` [PATCH v2 4/7] ARM: pxa: add devicetree code for irq handling Daniel Mack
2012-07-28  7:17   ` Haojian Zhuang
2012-07-28  9:56     ` Daniel Mack
2012-07-28 15:42       ` Haojian Zhuang
2012-07-29 14:09         ` Arnd Bergmann
2012-07-29 20:40           ` Daniel Mack
2012-07-30  8:31             ` Arnd Bergmann
2012-07-30  8:34               ` Daniel Mack [this message]
2012-07-30  8:55                 ` Haojian Zhuang
2012-07-30  9:31                   ` Daniel Mack
2012-07-31 12:18                     ` Arnd Bergmann
2012-07-29 15:08         ` Daniel Mack
2012-07-29 15:54           ` Haojian Zhuang
2012-07-29 19:01             ` Daniel Mack
2012-07-30  1:20               ` Haojian Zhuang
2012-07-30  1:24                 ` Haojian Zhuang
2012-07-30  7:11                   ` Daniel Mack
2012-07-29 16:13           ` Haojian Zhuang
2012-07-26 19:16 ` [PATCH v2 5/7] ARM: pxa3xx: skip default device initialization when booting via DT Daniel Mack
2012-07-26 19:16 ` [PATCH v2 6/7] ARM: pxa3xx: add generic DT machine code Daniel Mack
2012-07-26 19:16 ` [PATCH v2 7/7] ARM: pxa: add .dtsi files Daniel Mack

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=501646FC.60900@gmail.com \
    --to=zonque@gmail.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).