From: Olof Johansson <olof@lixom.net>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org, anton@samba.org
Subject: Re: [4/5] powerpc: PA Semi PWRficient platform support
Date: Wed, 6 Sep 2006 10:10:34 -0500 [thread overview]
Message-ID: <20060906101034.404014f7@localhost.localdomain> (raw)
In-Reply-To: <0C880511-D99D-4160-9EB1-A66B22B2D82F@kernel.crashing.org>
On Wed, 6 Sep 2006 15:38:54 +0200 Segher Boessenkool <segher@kernel.crashing.org> wrote:
> > +#define PA_PXP_CFA(bus, devfn, off) (((bus) << 20) | ((devfn) <<
> > 12) | (off))
>
> > + hose->cfg_data = ioremap(0xe0000000, 0x1000000);
>
> Shouldn't that length be 0x10000000 then? Or can't you have
> more than 0x10 busses?
Yes, typo that hasn't hit us yet. Thanks.
> > + bus_range = (int *) get_property(dev, "bus-range", &len);
> > + if (bus_range == NULL || len < 2 * sizeof(int)) {
> > + printk(KERN_WARNING "Can't get bus-range for %s, assume bus 0\n",
> > + dev->full_name);
> > + }
>
> Just kill all this "bus-range" stuff? Or do you really need it?
Not at this time. Removed.
> > + np = of_find_node_by_type(np, "open-pic");
> > + if (!np) {
> > + printk(KERN_ERR "No interrupt controller in device tree.\n");
> > + return;
> > + }
>
> "device_type" for the MPIC should be "interrupt-controller", "open-pic"
> should be in the "compatible" property instead.
Thanks, I now use the same logic as Maple.
> > + /* Find address list in /platform-open-pic */
>
> Erm, can't you get this info from the open-pic node itself?
> I know maple does it like this but that should be fixed ;-)
How about I keep it this way until Maple is fixed then? It's better to keep it
fairly common anyway. Functionally there's no difference.
> > + mpic = mpic_alloc(mpic_node, openpic_addr, MPIC_PRIMARY, 0, 0,
> > + " PAS-OPIC ");
> > + BUG_ON(mpic == NULL);
> > +
> > + mpic_assign_isu(mpic, 0, openpic_addr + 0x10000);
> > + mpic_init(mpic);
>
> Very nice, I'll convert maple to do the same (unless someone beats
> me to it, heh).
Maple isn't that different there. It just has to deal with multiple ISUs,
while we currently only have one.
-Olof
next prev parent reply other threads:[~2006-09-06 15:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060904175742.5472a6fa@localhost.localdomain>
2006-09-05 17:26 ` [1/5] powerpc: Reduce default cacheline size to 64 bytes Olof Johansson
2006-09-05 17:27 ` [2/5] powerpc: Divorce CPU_FTR_CTRL from CPU_FTR_PPCAS_ARCH_V2_BASE Olof Johansson
2006-09-05 17:28 ` [3/5] powerpc: PA6T cputable entry, PVR value Olof Johansson
2006-09-05 18:43 ` Michael Neuling
2006-09-05 17:28 ` [4/5] powerpc: PA Semi PWRficient platform support Olof Johansson
2006-09-05 21:31 ` Benjamin Herrenschmidt
2006-09-05 22:10 ` Olof Johansson
2006-09-05 17:29 ` Olof Johansson
2006-09-05 19:49 ` Roland Dreier
2006-09-05 20:15 ` Olof Johansson
2006-09-05 21:37 ` Arnd Bergmann
2006-09-05 21:48 ` Olof Johansson
2006-09-06 13:38 ` Segher Boessenkool
2006-09-06 15:10 ` Olof Johansson [this message]
2006-09-06 15:26 ` Segher Boessenkool
2006-09-07 0:58 ` Benjamin Herrenschmidt
2006-09-07 11:30 ` Segher Boessenkool
2006-09-07 0:58 ` Benjamin Herrenschmidt
2006-09-07 11:28 ` Segher Boessenkool
2006-09-07 12:47 ` Olof Johansson
2006-09-07 22:33 ` Benjamin Herrenschmidt
2006-09-05 17:30 ` [5/5] powerpc: PA Semi PWRficient MAINTAINER entry Olof Johansson
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=20060906101034.404014f7@localhost.localdomain \
--to=olof@lixom.net \
--cc=anton@samba.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=segher@kernel.crashing.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).