From: Arnd Bergmann <arnd@arndb.de>
To: Rob Herring <robh@kernel.org>
Cc: Jason Cooper <jason@lakedaemon.net>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Linus Walleij <linus.ml.walleij@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] ARM legacy board DT conversion finalization
Date: Tue, 20 May 2014 10:08:21 +0200 [thread overview]
Message-ID: <4921873.t2F8plV493@wuerfel> (raw)
In-Reply-To: <CAL_Jsq+kOu82okhJn0_ftwemE_m4nsTRawrF-fWAU2XTJ9xRcA@mail.gmail.com>
On Monday 19 May 2014 18:06:02 Rob Herring wrote:
> > On Friday 16 May 2014 23:20:42 Ben Hutchings wrote:
> >> On Fri, 2014-05-16 at 14:42 -0400, Jason Cooper wrote:
> >> > On Fri, May 16, 2014 at 07:31:51PM +0100, Ben Hutchings wrote:
> >> > > Our 'legacy' (which I take to mean pre-v7) configurations are now
> >> > > kirkwood, mv78xx0, orion5x (all about to converge to mvebu) and
> >> > > versatile.
> >> >
> >> > I'm not familiar with versatile, the others I've seen a few times.
> >>
> >> Versatile is one of ARM's own development boards, but more importantly
> >> it's something QEMU can emulate.
> >
> > We should really have this in multiplatform soon, I think the last issue
> > for versatile is common clock support, but Linus Walleij may have more
> > details about what remains here.
>
> While not necessarily the same thing, but does move versatile in the
> right direction, I've got patches in progress which fully move
> versatile over to DT. The main issues there are:
>
> common clock
> irq cntlr init from DT
> Move PCI to DT and platform driver
>
> I'd like to do this all in one step to avoid doing things like non-DT
> common clock init.
Sounds good, yes.
> It's blocked on the common DT PCI code and my free
> time.
>
> There are then a few bits related to mach/plat headers needed move
> versatile to multiplatform. I think these issues are mostly the same
> changes that have been done or are needed on integrator which is what
> Linus has been working on.
Ah, right. I see these two includes from mach-versatile to plat/*.h headers:
arch/arm/mach-versatile/core.c:#include <plat/clcd.h>
arch/arm/mach-versatile/core.c:#include <plat/sched_clock.h>
We can deal with those by adding
ccflags-y := -I$(srctree)/arch/arm/plat-versatile/include
to mach-versatile/Makefile, or we can rearrange the code. The opposite
direction would be harder, but I don't see any remaining dependencies
there.
Arnd
next prev parent reply other threads:[~2014-05-20 8:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 3:00 Jason Cooper
2014-05-11 12:37 ` Jonathan Corbet
2014-05-11 13:59 ` Alexandre Belloni
2014-05-11 14:22 ` Olof Johansson
2014-05-15 12:15 ` Grant Likely
2014-05-15 13:38 ` Jason Cooper
2014-05-15 18:50 ` Rob Herring
2014-05-15 19:42 ` Jason Cooper
2014-05-16 3:30 ` Olof Johansson
2014-05-16 4:10 ` Jason Cooper
2014-05-16 18:31 ` Ben Hutchings
2014-05-16 18:42 ` Jason Cooper
2014-05-16 22:20 ` Ben Hutchings
2014-05-19 12:20 ` Arnd Bergmann
2014-05-19 22:41 ` Peter Maydell
2014-05-19 23:06 ` Rob Herring
2014-05-20 8:08 ` Arnd Bergmann [this message]
2014-05-22 14:44 ` Rob Herring
2014-05-23 13:48 ` Linus Walleij
2014-05-23 14:42 ` Arnd Bergmann
2014-05-23 13:46 ` Linus Walleij
2014-05-23 13:40 ` Linus Walleij
2014-05-23 13:57 ` Arnd Bergmann
2014-05-16 3:39 ` Olof Johansson
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=4921873.t2F8plV493@wuerfel \
--to=arnd@arndb.de \
--cc=jason@lakedaemon.net \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linus.ml.walleij@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh@kernel.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