From: simon@sequanux.org (Simon Guinot)
To: linux-arm-kernel@lists.infradead.org
Subject: orion/kirkwood and device tree
Date: Fri, 4 Nov 2011 10:21:59 +0100 [thread overview]
Message-ID: <20111104092159.GG634@kw.sim.vm.gnt> (raw)
In-Reply-To: <201111032250.59528.michael@walle.cc>
Hi Michael,
On Thu, Nov 03, 2011 at 10:50:59PM +0100, Michael Walle wrote:
> Am Donnerstag 03 November 2011, 19:47:45 schrieb Jason:
> > Michael,
> >
> > On Wed, Nov 02, 2011 at 11:03:04PM +0100, Michael Walle wrote:
> > > Am Mittwoch 02 November 2011, 17:50:57 schrieb Jason:
> > > > Michael,
> > > >
> > > > On Mon, Oct 31, 2011 at 11:50:28PM +0100, Michael Walle wrote:
> > > > > i've already ported some marvell devices to DT. spi-orion, orion-wdt,
> > > > > rtc-mv and mv_cesa. Atm i'm struggling with how to pass
> > > > > kirkwood_mbus_dram_info to the device drivers (the old method is to
> > > > > pass it through platform_data)
> > > >
> > > > Do you have a public git tree I could pull from, by chance? I don't
> > > > care about the state, I'd like to learn by example and start pitching
> > > > in.
> > >
> > > yeah i pushed it to github:
> > > https://github.com/mwalle/linux/tree/kirkwood-devtree
> >
> > This is great! I was having trouble figuring out how to do the
> > interrupt controller, and you have that. I'll look more closely this
> > evening.
> >
> > My only comment so far is that I think a lot of what you have in
> > lschlv2.dts can be in kirkwood.dtsi. That way other boards don't have
> > to copy it (serial, spi, ehci, wdt, rtc, crypto).
> yeah i had it there and it should be definitely put back to kirkwood.dtsi. the
> reason i've put it into lschv2.dts atm is that there is the clock property for
> every device, which may be different for different platforms.
>
> > Oh, also, I think the board-dt.c should be pulling the phys addresses
> > from the dt, it looks like you're still relying on the #defines...
> i haven't looked at ethernet/mdio yet ;)
It is good to see some work to add DT support for Kirkwood SoCs.
What are your plans concerning the MPPs configuration ? Is it possible
to embed this configuration into a DT ? What kind of node could hold
a such information ?
Regards,
Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20111104/c9bb7072/attachment.sig>
next prev parent reply other threads:[~2011-11-04 9:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111031105740.GC29402@lunn.ch>
[not found] ` <20111031152100.GR32165@titan.lakedaemon.net>
[not found] ` <20111031164042.GD29402@lunn.ch>
2011-10-31 22:50 ` orion/kirkwood and device tree Michael Walle
2011-10-31 22:54 ` Russell King - ARM Linux
2011-11-01 6:25 ` Andrew Lunn
2011-11-02 16:50 ` Jason
2011-11-02 22:03 ` Michael Walle
2011-11-03 18:15 ` memory map in fdt was: " Jason
2011-11-03 18:15 ` Jason
2011-11-03 18:47 ` Jason
2011-11-03 21:50 ` Michael Walle
2011-11-04 9:21 ` Simon Guinot [this message]
2011-11-16 23:34 ` Michael Walle
2011-11-04 14:01 ` Nicolas Pitre
2011-11-06 23:12 ` Michael Walle
2011-11-06 16:05 ` Andrew Lunn
2011-11-06 22:40 ` Michael Walle
2011-11-07 6:27 ` Andrew Lunn
2011-11-07 2:35 ` Nicolas Pitre
2011-11-07 6:28 ` Andrew Lunn
2011-11-06 16:07 ` [PATCH 1/1] [orion] Consolidate the address map setup on Orion based platforms Andrew Lunn
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=20111104092159.GG634@kw.sim.vm.gnt \
--to=simon@sequanux.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.