ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>,
	Jason Cooper <jason@lakedaemon.net>,
	Linus Walleij <linus.ml.walleij@gmail.com>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] ARM legacy board DT conversion finalization
Date: Fri, 23 May 2014 15:46:09 +0200	[thread overview]
Message-ID: <CACRpkdaPStOjWeH9SgHKjcyrOfebbnvs_p5rWueNBdt9oBBMzg@mail.gmail.com> (raw)
In-Reply-To: <CAL_Jsq+kOu82okhJn0_ftwemE_m4nsTRawrF-fWAU2XTJ9xRcA@mail.gmail.com>

On Tue, May 20, 2014 at 1:06 AM, Rob Herring <robh@kernel.org> wrote:
> On Mon, May 19, 2014 at 7:20 AM, Arnd Bergmann <arnd@arndb.de> wrote:

>> 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.

Doing this two-stage rocket:
Legacy -> DT -> multiplatform

Is usually the smoothest. That is what I did on U300, U8500
and will do on the Integrator.

> I'd like to do this all in one step to avoid doing things like non-DT
> common clock init. It's blocked on the common DT PCI code and my free
> time.

I agree. And invariably this will confuse a lot of QEMU users
until they figure out how to boot their new image with a device
tree. But that is business as usual I guess.

> 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.

I'm onto these as part of both Integrator and RealView modernization.

Yours,
Linus Walleij

  parent reply	other threads:[~2014-05-23 13:46 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
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 [this message]
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=CACRpkdaPStOjWeH9SgHKjcyrOfebbnvs_p5rWueNBdt9oBBMzg@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --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