public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab•ca>
To: linuxppc-dev@ozlabs•org,
	Wolfgang Reissnegger <wolfgang.reissnegger@xilinx•com>,
	Leonid <Leonid@a-k-a•net>,
	Stephen Neuendorffer <stephen.neuendorffer@xilinx•com>,
	microblaze-uclinux@itee•uq.edu.au
Subject: [PATCH v2] Device tree bindings for Xilinx devices
Date: Mon, 15 Oct 2007 09:53:44 -0600	[thread overview]
Message-ID: <20071015155223.7403.39615.stgit@trillian.cg.shawcable.net> (raw)

From: Grant Likely <grant.likely@secretlab•ca>

Here's my second version of xilinx device tree bindings.  Please review
and comment.  I'd like to push these out to Paulus in the next couple
of days.

Cheers,
g.

Signed-off-by: Grant Likely <grant.likely@secretlab•ca>
---

 Documentation/powerpc/booting-without-of.txt |   55 ++++++++++++++++++++++++++
 1 files changed, 55 insertions(+), 0 deletions(-)

diff --git a/Documentation/powerpc/booting-without-of.txt b/Documentation/powerpc/booting-without-of.txt
index 7a6c5f2..21afaea 100644
--- a/Documentation/powerpc/booting-without-of.txt
+++ b/Documentation/powerpc/booting-without-of.txt
@@ -2089,6 +2089,61 @@ 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"
+    - 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 (empty) : rotate display 180 degrees.
+
+   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:
+    - 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"
+    - 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:
+    - interrupt-parent, interrupts : Connection of device irq signal.
+
 VII - Specifying interrupt information for devices
 ===================================================
 

             reply	other threads:[~2007-10-15 15:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-15 15:53 Grant Likely [this message]
2007-10-15 19:21 ` [PATCH v2] Device tree bindings for Xilinx devices Arnd Bergmann
2007-10-15 19:54   ` Grant Likely
2007-10-16 18:24 ` Stephen Neuendorffer
2007-10-16 19:36   ` Grant Likely
2007-10-17  0:21     ` Stephen Neuendorffer
2007-10-17  2:35       ` Grant Likely
2007-10-17  3:03         ` Grant Likely
2007-10-16 23:23 ` Stephen Neuendorffer
2007-10-17  1:49   ` Josh Boyer
2007-10-17  2:31   ` Grant Likely

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=20071015155223.7403.39615.stgit@trillian.cg.shawcable.net \
    --to=grant.likely@secretlab$(echo .)ca \
    --cc=Leonid@a-k-a$(echo .)net \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=microblaze-uclinux@itee$(echo .)uq.edu.au \
    --cc=stephen.neuendorffer@xilinx$(echo .)com \
    --cc=wolfgang.reissnegger@xilinx$(echo .)com \
    /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