From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Scott Wood <scottwood@freescale.com>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: open-pic device tree node and subnodes for additional functionality?
Date: Thu, 19 Feb 2009 18:14:52 +1100 [thread overview]
Message-ID: <1235027692.8805.10.camel@pasglop> (raw)
In-Reply-To: <8330CA5E-0F3B-49D5-AB55-500CD37739C1@kernel.crashing.org>
> For MSI I doubt any. I think on some parts we might have two (or
> more) groups of MSIs.
>
> However I want to be able to handle timers and the slightly more
> generic message interrupts.
You can probably add a reg and a ranges, the reg remains the same
as today as to not inflict any collateral damage, and the ranges
represents downstream addresses to child nodes msi, timers, ...
(ie, it's no big deal if the parent "reg" somewhat overlap the
childs ranges... it's only a problem if the drivers try to request
the resources in ways that collide)
Ben.
prev parent reply other threads:[~2009-02-19 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 16:58 open-pic device tree node and subnodes for additional functionality? Kumar Gala
2009-02-16 18:12 ` Scott Wood
2009-02-16 18:50 ` Kumar Gala
2009-02-19 7:14 ` Benjamin Herrenschmidt [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=1235027692.8805.10.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@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 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).