From: Arnd Bergmann <arnd@arndb•de>
To: linuxppc-dev@ozlabs•org
Subject: Re: [PATCH v2] Device tree bindings for Xilinx devices
Date: Mon, 15 Oct 2007 21:21:53 +0200 [thread overview]
Message-ID: <200710152121.54977.arnd@arndb.de> (raw)
In-Reply-To: <20071015155223.7403.39615.stgit@trillian.cg.shawcable.net>
On Monday 15 October 2007, Grant Likely wrote:
> 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.
There are a few more properties that I can imagine you might need.
Not sure if it makes sense specifying them now, but here are my thoughts:
> 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.
rotate-display could be defined as something that allows 0/90/180/270
degrees, as well as mirroring, not just 180 degree rotation.
> + 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.
> +
typically, serial ports include properties for current-speed and
clock-frequency. I guess it would be good to include at least one
of the two here.
Arnd <><
next prev parent reply other threads:[~2007-10-15 19:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 15:53 [PATCH v2] Device tree bindings for Xilinx devices Grant Likely
2007-10-15 19:21 ` Arnd Bergmann [this message]
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=200710152121.54977.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--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