devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 3/6] ARM: plat-versatile: add DT support to FPGA IRQ controller
Date: Sat, 1 Sep 2012 07:11:18 +0000	[thread overview]
Message-ID: <201209010711.18985.arnd@arndb.de> (raw)
In-Reply-To: <CACRpkdamVhbW_nizDODTu2wg7wX+4ENnLMGH=RoHkG4hwn3Yfg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Saturday 01 September 2012, Linus Walleij wrote:
> > When all devices get their IRQ numbers from the device
> > tree, you can move to linear IRQ domains instead of legacy, and let
> > the irq domain code pick the numbers.
> 
> It seems I have no other choice here than to move directly to
> linear numbers or atleast dynamically allocated descriptors.

You could also do a hack and keep the number hardcoded, or dependent
on the "compatible" value of the root node, but moving to linear
domains would be nicer because then you don't have to change this code
again.

	Arnd

      parent reply	other threads:[~2012-09-01  7:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16 12:15 [PATCH 3/6] ARM: plat-versatile: add DT support to FPGA IRQ controller Linus Walleij
     [not found] ` <1345119357-22702-1-git-send-email-linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2012-08-16 13:50   ` Arnd Bergmann
     [not found]     ` <201208161350.49063.arnd-r2nGTMty4D4@public.gmane.org>
2012-09-01  1:14       ` Linus Walleij
     [not found]         ` <CACRpkdamVhbW_nizDODTu2wg7wX+4ENnLMGH=RoHkG4hwn3Yfg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-09-01  7:11           ` Arnd Bergmann [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=201209010711.18985.arnd@arndb.de \
    --to=arnd-r2ngtmty4d4@public.gmane.org \
    --cc=arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
    --cc=will.deacon-5wv7dgnIgG8@public.gmane.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).