From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: list <linuxppc-dev@ozlabs.org>
Subject: Re: [RFC] Device tree for new desktop platform in arch/powerpc
Date: Thu, 21 Jun 2007 22:42:13 +1000 [thread overview]
Message-ID: <1182429733.24740.12.camel@localhost.localdomain> (raw)
In-Reply-To: <20070619054232.GB32039@localhost.localdomain>
On Tue, 2007-06-19 at 15:42 +1000, David Gibson wrote:
>
> Is there a device binding defined somewhere for "chrp,iic"?
Yes, it's the standard for 8259 on chrp and chrp-like platforms.
> > interrupt-controller;
> > reg = <20 2 a0 2 4d0 2>;
> > reserved-interrupts = <2>;
I'm currious about the above though, what is it ?
> > #address-cells = <1>;
Why #address-cells set to 1 ? In a PIC node, in fact, I would expect it
to be 0 to avoid any spurrious "reg" matching for interrupts.
> > #size-cells = <0>;
> > #interrupt-cells = <2>;
> > };
>
> > 8042@60 {
> > device_type = "8042";
> > compatible = "chrp,8042";
> > reg = <60 10>;
> > interrupts = <1 3 c 3>; // IRQ1, IRQ12
> (rising edge)
> > interrupt-parent = <&interrupt-controller>;
Just put the interrupt-parent pointer once in the isa bridge and all isa
devices below the bridge.
> This should cause a dtc error. Either you want &/interrupt-controller
> or give the interrupt-controller node a label and refer to that. It's
> either '&/some/full/path' or '&label'.
>
> > #address-cells = <1>;
> > #size-cells = <0>; // No physical
> address.
>
> Comment is arguably incorrect.
Yeah, not sure what that is supposed to be.
Ben.
next prev parent reply other threads:[~2007-06-21 12:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 18:57 [RFC] Device tree for new desktop platform in arch/powerpc Gerhard Pircher
2007-06-18 19:15 ` Mark A. Greer
2007-06-18 19:43 ` Gerhard Pircher
2007-06-18 20:25 ` Mark A. Greer
2007-06-19 5:08 ` David Gibson
2007-06-19 5:42 ` David Gibson
2007-06-19 6:16 ` Segher Boessenkool
2007-06-19 8:40 ` Gerhard Pircher
2007-06-19 9:14 ` Segher Boessenkool
2007-06-19 9:52 ` Gerhard Pircher
2007-06-19 10:08 ` Segher Boessenkool
2007-06-19 12:37 ` Gerhard Pircher
2007-06-19 13:15 ` Segher Boessenkool
2007-06-19 13:29 ` Gerhard Pircher
2007-06-21 12:42 ` Benjamin Herrenschmidt [this message]
2007-06-21 13:28 ` Gerhard Pircher
2007-06-21 14:59 ` Segher Boessenkool
2007-06-21 14:29 ` Segher Boessenkool
2007-06-21 23:25 ` Benjamin Herrenschmidt
2007-06-22 7:52 ` Segher Boessenkool
2007-06-22 8:16 ` Benjamin Herrenschmidt
2007-06-22 9:10 ` Segher Boessenkool
2007-06-19 6:08 ` Segher Boessenkool
2007-06-19 9:08 ` Gerhard Pircher
2007-06-19 9:28 ` Segher Boessenkool
2007-06-21 12:36 ` Benjamin Herrenschmidt
2007-06-21 13:20 ` Gerhard Pircher
2007-06-21 14:38 ` Segher Boessenkool
2007-06-21 16:27 ` Gerhard Pircher
2007-06-21 23:22 ` Benjamin Herrenschmidt
2007-06-22 13:12 ` Gerhard Pircher
2007-06-22 13:40 ` Benjamin Herrenschmidt
2007-06-21 14:24 ` Segher Boessenkool
2007-06-21 16:21 ` Gerhard Pircher
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=1182429733.24740.12.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.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).