All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org,
	Yoder Stuart-B08248 <stuart.yoder@freescale.com>
Subject: Re: [RFC][PATCH 6/8] Walnut DTS
Date: Mon, 16 Jul 2007 17:18:52 -0500	[thread overview]
Message-ID: <469BEECC.6070404@freescale.com> (raw)
In-Reply-To: <1184623898.25235.96.camel@localhost.localdomain>

Benjamin Herrenschmidt wrote:
> No, interrupt maps are useful in devices with no children in some corner
> cases. Remember that a map doesnt need to use the address part of the
> source specifier, thus it can be used to do a pure domain->domain
> conversion of the irq numbers, what sort of thing. The map has the added
> advantage that today, it's the only mechanism that allows you to specify
> different interrupt-parents through the same nexus, which is useful for
> 4xx.

OK...  but if you're doing a pure IRQ number conversion, the only useful 
#address-cells would be zero, which makes it a reasonable default IMHO 
(unlike the arbitrary 2 for regular traversal).

-Scott

  reply	other threads:[~2007-07-16 22:19 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-11 13:52 [RFC][PATCH 0/8] arch/powerpc support for Walnut Board Josh Boyer
2007-07-11 13:53 ` [RFC][PATCH 1/8] 4xx Kconfig cleanup Josh Boyer
2007-07-11 13:55 ` [RFC][PATCH 2/8] 4xx boot wrapper reworks Josh Boyer
2007-07-11 13:56 ` [RFC][PATCH 3/8] 4xx MMU Josh Boyer
2007-07-11 20:56   ` Arnd Bergmann
2007-07-11 21:15     ` Josh Boyer
2007-07-12  7:09     ` Kumar Gala
2007-07-12 12:40       ` Josh Boyer
2007-07-11 13:57 ` [RFC][PATCH 4/8] 4xx decrementer fixes Josh Boyer
2007-07-11 13:58 ` [RFC][PATCH 5/8] Fix 4xx build Josh Boyer
2007-07-11 21:00   ` Arnd Bergmann
2007-07-11 13:59 ` [RFC][PATCH 6/8] Walnut DTS Josh Boyer
2007-07-11 14:26   ` Stefan Roese
2007-07-11 14:37     ` Josh Boyer
2007-07-11 17:49   ` Segher Boessenkool
2007-07-11 17:55     ` Josh Boyer
2007-07-11 18:07       ` Segher Boessenkool
2007-07-18  1:02       ` David Gibson
2007-07-12 15:13     ` Yoder Stuart-B08248
2007-07-16 14:34       ` Segher Boessenkool
2007-07-16 21:47         ` Benjamin Herrenschmidt
2007-07-16 21:55           ` Scott Wood
2007-07-16 22:11             ` Benjamin Herrenschmidt
2007-07-16 22:18               ` Scott Wood [this message]
2007-07-16 22:34                 ` Benjamin Herrenschmidt
2007-07-16 21:55           ` Yoder Stuart-B08248
2007-07-16 22:12             ` Benjamin Herrenschmidt
2007-07-17  2:39           ` Josh Boyer
2007-07-17 14:26             ` Segher Boessenkool
2007-07-17 14:15           ` Segher Boessenkool
2007-07-17 21:25             ` Benjamin Herrenschmidt
2007-07-17 22:25               ` Scott Wood
2007-07-17 22:58                 ` Benjamin Herrenschmidt
2007-07-18 13:53                 ` Segher Boessenkool
2007-07-18 16:47                   ` Scott Wood
2007-07-19 16:54                     ` Segher Boessenkool
2007-07-18 13:48               ` Segher Boessenkool
2007-07-11 14:02 ` [RFC][PATCH 7/8] Walnut defconfig Josh Boyer
2007-07-11 14:03 ` [RFC][PATCH 8/8] Walnut board support Josh Boyer
2007-07-11 14:04 ` [RFC][PATCH 9/8] Walnut zImage wrapper Josh Boyer

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=469BEECC.6070404@freescale.com \
    --to=scottwood@freescale.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=stuart.yoder@freescale.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.