From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Olof Johansson <olof@lixom.net>,
linuxppc-dev@ozlabs.org,
Yoder Stuart-B08248 <stuart.yoder@freescale.com>
Subject: Re: [Fwd: [PATCH Resend 01/02] Add Linux ASMP support for MPC8641D]
Date: Fri, 23 Mar 2007 08:01:51 +1100 [thread overview]
Message-ID: <1174597311.10836.50.camel@localhost.localdomain> (raw)
In-Reply-To: <6186A8EC-8A6F-47E6-B534-D5494E5FA34C@kernel.crashing.org>
> If you look at what mpic_init() does you will see that the registers
> would be setup twice.
>
> Also, you don't need to walk the device-tree at all. As Olof pointed
> out there maybe interrupts that are not described in the device
> tree. We can setup this information when you do a request_irq() ->
> set_irq_type().
>
> If you aren't doing a request_irq() for the interrupt than it doesn't
> need to be setup. Additionally, you should only doing a request_irq
> () for an interrupt that is "owned" by that core.
The need to have an MPIC shared by more than one cores is something that
will be coming elsewhere too (can't give details...)
I think we should invent an MPIC specific property indicating that the
MPIC is to be shared and indicating on one of the users that it's the
"master" (the one doing the initial full setup, the others can then spin
on some bit somewhere before going on, unless we decide such a shared
setup, the PIC has to be pre-initialized by some firmware and we skip
all inits in mpic) and indicating which sources belong to which users.
Ben.
next prev parent reply other threads:[~2007-03-22 21:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 14:25 [Fwd: [PATCH Resend 01/02] Add Linux ASMP support for MPC8641D] Jon Loeliger
2007-03-22 14:46 ` Kumar Gala
2007-03-22 15:32 ` Yoder Stuart-B08248
2007-03-22 15:40 ` Kumar Gala
2007-03-22 15:51 ` Olof Johansson
2007-03-22 15:44 ` Kumar Gala
2007-03-22 15:58 ` Yoder Stuart-B08248
2007-03-22 16:11 ` Kumar Gala
2007-03-22 21:01 ` Benjamin Herrenschmidt [this message]
2007-03-22 21:25 ` Kumar Gala
2007-03-22 23:02 ` Segher Boessenkool
2007-03-22 16:13 ` Segher Boessenkool
2007-03-23 3:55 ` Milton Miller
[not found] <mailman.532.1174628450.2645.linuxppc-dev@ozlabs.org>
2007-03-28 20:40 ` Siva Prasad
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=1174597311.10836.50.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--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 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).