From: "Gerhard Pircher" <gerhard_pircher@gmx•net>
To: David Gibson <david@gibson•dropbear.id.au>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [RFC] Device tree for new desktop platform in arch/powerpc
Date: Tue, 19 Jun 2007 10:40:15 +0200 [thread overview]
Message-ID: <20070619084015.202120@gmx.net> (raw)
In-Reply-To: <20070619054232.GB32039@localhost.localdomain>
-------- Original-Nachricht --------
Datum: Tue, 19 Jun 2007 15:42:32 +1000
Von: David Gibson <david@gibson•dropbear.id.au>
An: Gerhard Pircher <gerhard_pircher@gmx•net>
CC: linuxppc-dev@ozlabs•org, "list <linuxppc-dev"@ozlabs.org
Betreff: Re: [RFC] Device tree for new desktop platform in arch/powerpc
> > 3. The dts files define the device_type of a serial port as
> > "serial", whereas the OF spec says "pnpPNP,501". What's the
> > difference between the two?
>
> Err... device_type == "pnpPNP,501", or compatible == "pnpPNP,501"?
Sorry, I meant compatible = "ns16550" and compatible = "pnpPNP,501".
> This node has no children, so #address-cells and #size-cells values
> are meaningless.
Ah, I thought these properties are always necessary, if a ranges or reg
property is defined.
> > interrupt-controller {
> > device_type = "interrupt-controller";
> > compatible = "chrp,iic";
>
> Is there a device binding defined somewhere for "chrp,iic"?
Dunno. :-) It's based on these document here:
http://playground.sun.com/1275/bindings/devices/html/isa-pic-1_1d.html
http://playground.sun.com/1275/bindings/pci/pci2_1.pdf
> 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'.
That makes sense.
> > timer@40 {
> > device_type = "timer";
>
> For flat device trees we're generally avoiding setting the device_type
> property unless there is a clearly defined "class binding" which
> applies. There are a number of cases here where I'm not sure if
> that's true.
What about platforms that provide a real OF device tree? Do they define
device nodes for timers?
> > clock-frequency = <0>; // Not necessary?
>
> Probably necessary, but may need to be filled in from the bootwrapper.
This should be a constant anyway, so I can define it here.
> > fdc@3f0 {
> > device_type = "fdc";
> > compatible = "pnpPNP,700";
> > reg = <3f0 8>;
> > interrupts = <6 3>;
> > interrupt-parent = <&interrupt-controller>;
> > /* dma = < >;*/
> > #address-cells = <1>;
> > #size-cells = <0>;
> >
> > disk {
> > device_type = "block";
> > reg = <0>;
> > };
> >
> Don't think you need this subnode.
It's mentioned here (if I interpreted it correctly):
http://playground.sun.com/1275/bindings/devices/html/fdc.html
Not sure, if the Linux kernel needs it.
Thanks!
regards,
Gerhard
--
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail
next prev parent reply other threads:[~2007-06-19 8:40 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 [this message]
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
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=20070619084015.202120@gmx.net \
--to=gerhard_pircher@gmx$(echo .)net \
--cc=david@gibson$(echo .)dropbear.id.au \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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