From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Xilinx: Adding zynq platform support
Date: Mon, 30 May 2011 14:23:47 -0600 [thread overview]
Message-ID: <20110530202347.GC32035@ponder.secretlab.ca> (raw)
In-Reply-To: <BANLkTikjMYUCXgBN3UKjpzEg68qOqOHv5A@mail.gmail.com>
On Mon, May 30, 2011 at 05:47:35PM +0800, Barry Song wrote:
> 2011/5/26 Arnd Bergmann <arnd@arndb.de>:
> > On Wednesday 25 May 2011, Grant Likely wrote:
> >>
> >> As per discussion attached below. ?Please pull this tree adding device
> >> tree support to ARM, plus some other minor device tree changes.
> >
> > Hi Grant and Linus,
> >
> > There is also the new Xilinx zynq subarchitecture pending that depends
> > on this, see below. Should we also include that right away, in order
> > to have an example for other platforms? I think the code is clean
> > enough and it would be good to have.
> >
> > ? ? ? ?Arnd
> >
> > 8<---------
> > From: Grant Likely <grant.likely@secretlab.ca>
> >
> > The 1st board support is minimal to get a system up and running
> > on the Xilinx platform.
> >
> > This platform reuses the clock implementation from plat-versatile, and
> > it depends entirely on CONFIG_OF support. ?There is only one board
> > support file which obtains all device information from a device tree
> > dtb file which is passed to the kernel at boot time.
> >
> > Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> > [john.linn at xilinx.com: Reverted dependency on of_irq_domain patches]
> > Signed-off-by: John Linn <john.linn@xilinx.com>
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> is there a whole complete tree for zynq? i'd like to refer. thanks! as
> i am moving csr prima2 to device tree, we need to change so many
> codes. i hope we can follow what the way zynq is doing.
It is in linux-next. Hopefully we'll get it merged into the arm
subarch maintainer tree early in this cycle.
You can also look at arch/powerpc/platforms/* to see examples of how
to work with the DT. I'm also working on some howto documentation for
doing DT work.
g.
prev parent reply other threads:[~2011-05-30 20:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 15:50 [git pull] ARM Device tree support Grant Likely
2011-05-24 18:42 ` Nicolas Pitre
[not found] ` <BANLkTi=hCpCbNzi1ZiKmGnbhmCG2Ce=EkA@mail.gmail.com>
2011-05-26 13:59 ` [PATCH] ARM: Xilinx: Adding zynq platform support Arnd Bergmann
2011-05-26 15:06 ` Grant Likely
2011-05-26 22:01 ` Russell King - ARM Linux
2011-05-26 22:13 ` Grant Likely
2011-05-26 22:16 ` Grant Likely
2011-05-26 22:25 ` Russell King - ARM Linux
2011-05-30 20:20 ` Grant Likely
2011-05-30 9:47 ` Barry Song
2011-05-30 20:23 ` Grant Likely [this message]
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=20110530202347.GC32035@ponder.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.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).