From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Device tree bindings for Xilinx devices
Date: Wed, 10 Oct 2007 15:38:02 -0500 [thread overview]
Message-ID: <1192048682.5534.92.camel@localhost.localdomain> (raw)
In-Reply-To: <20071008075127.9887.38702.stgit@trillian.cg.shawcable.net>
On Mon, 2007-10-08 at 01:53 -0600, Grant Likely wrote:
> From: Grant Likely <grant.likely@secretlab.ca>
>
> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> ---
>
> This is a first draft, please review and comment.
I'll start off with the fact that I hardly consider myself a DT expert,
so take what I say with a grain of salt.
> On a side node, I think booting-without-of.txt could get really unwieldly
> in the near future. Perhaps the device tree bindings should be organized
> differently and separated from the functional description of device tree
> usage. Thoughts?
>
> Cheers,
> g.
>
> Documentation/powerpc/booting-without-of.txt | 58 ++++++++++++++++++++++++++
> 1 files changed, 58 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/powerpc/booting-without-of.txt b/Documentation/powerpc/booting-without-of.txt
> index 20e0e6c..a6d6056 100644
> --- a/Documentation/powerpc/booting-without-of.txt
> +++ b/Documentation/powerpc/booting-without-of.txt
> @@ -1850,6 +1850,64 @@ platforms are moved over to use the flattened-device-tree model.
>
> More devices will be defined as this spec matures.
>
> + l) Xilinx ML300 Framebuffer
> +
> + Simple framebuffer device from the ML300 reference design (also on the
> + ML403 reference design as well as others).
> +
> + Required properties:
> + - compatible : Must include "xilinx,ml300-fb"
Similarly, "xilinx,ml403-fb" will be required for ML403 correct? Or do
they share exact identical implementations?
> + - reg : offset and length of the framebuffer register set
> +
> + Optional properties:
> + - resolution : <xres yres> pixel resolution of framebuffer. Some
> + implementations use a different resolution. Default
> + is <d#640 d#480>
> + - virt-resolution : <xvirt yvirt> Size of framebuffer in memory.
> + Default is <d#1024 d#480>.
> + - rotate-display : rotate display 180 degrees.
> + - display-number : Logical number of display
> +
> + m) Xilinx SystemACE
> +
> + The Xilinx SystemACE device is used to program FPGAs from an FPGA
> + bitstream stored on a CF card. It can also be used as a generic CF
> + interface device.
> +
> + Required properties:
> + - compatible : Must include "xilinx,sysace"
> + - reg : offset and length of SystemACE register set
> +
> + Recommended properties:
> + - interrupt-parent, interrupts : Connection of device irq signal.
> +
> + Optional properties:
> + - number : logical number of the SystemACE device based at 0.
"number" seems a bit to generic to me. logical-number seems a bit more
descriptive.
> + - 8-bit (empty) : Set this property if the SystemACE must be in 8 bit mode
> +
> + n) Xilinx EMAC and Xilinx TEMAC
> +
> + Xilinx Ethernet devices. Uses common properties from other Ethernet
> + devices with the following constraints:
> +
> + Required properties:
> + - compatible : Must include one of: "xilinx,plb-temac",
> + "xilinx,plb-emac", "xilinx-opb-emac"
I think you mean "xilinx,opb-emac" on that last one.
> + - dma-mode : Must be one of "none", "simple", "sg" (sg == scatter gather)
> +
> + o) Xilinx Uartlite
> +
> + Xilinx uartlite devices are simple fixed speed serial ports. Uartlite
> + ports should be described in a node with the following properties.
> +
> + Requred properties:
> + - compatible : Must include "xilinx,uartlite"
> + - reg : offset and length of uartlite register set
> +
> + Recommended properties:
> + - port-number : logical port number of uartlite device based at 0.
> + - interrupt-parent, interrupts : Connection of device irq signal.
> +
josh
next prev parent reply other threads:[~2007-10-10 20:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 7:53 [PATCH] Device tree bindings for Xilinx devices Grant Likely
2007-10-10 16:39 ` Grant Likely
2007-10-10 20:38 ` Josh Boyer [this message]
2007-10-11 1:38 ` David Gibson
2007-10-11 2:25 ` Grant Likely
2007-10-11 4:06 ` David Gibson
2007-10-11 4:18 ` Grant Likely
2007-10-11 4:24 ` David Gibson
2007-10-11 4:58 ` Grant Likely
2007-10-11 5:08 ` David Gibson
2007-10-11 5:27 ` Grant Likely
2007-10-12 3:14 ` David Gibson
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=1192048682.5534.92.camel@localhost.localdomain \
--to=jwboyer@linux.vnet.ibm.com \
--cc=grant.likely@secretlab.ca \
--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).