linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Making ARM multiplatform kernels DT-only?
Date: Fri, 4 May 2012 23:43:18 +0100	[thread overview]
Message-ID: <20120504224318.GL897@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CACRpkdZ3m=PXg35==3wo2xHPL7TRn1W0AX_CeMKjPd1U+pTAGQ@mail.gmail.com>

On Fri, May 04, 2012 at 10:03:40PM +0200, Linus Walleij wrote:
> On Fri, May 4, 2012 at 4:35 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> 
> > Well, my understanding is that there's DT patches around for Versatile.
> 
> Is there? There is some in-tree stuff, but haven't seen any other
> sign of patches.
>[...]
> make it clear that noone ever tested an MMC card on a Versatile
> booted on real hardware using DT. And I strongly suspect there
> are more instances like that, it seems AACI, GPIO and I2C and
> I guess whatever you cannot test on QEMU is just unsupported.

Given that we've converted stuff like MMCI to use DT, it _should_ be
the case that we can just add the appropriate DT description to the
existing Versatile DT - we might need to create some new GPIO devices
for things like SYSMCI and get rid of the status function, or we
could just use the auxdata stuff in the mean time.

Either way, we've solved these problems on other platforms, and the
shared code has already been fixed or is being fixed for stuff like
Versatile Express.

Lets also not forget that the VIC code has already been converted to
DT.

So I don't think there's a big problem here - I think most of the
pieces of the jigsaw are in place through converting other platforms.

      parent reply	other threads:[~2012-05-04 22:43 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03 13:50 Making ARM multiplatform kernels DT-only? Arnd Bergmann
2012-05-03 13:45 ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-03 14:04 ` Russell King - ARM Linux
2012-05-03 13:52   ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-04  6:31   ` Deepak Saxena
2012-05-04  7:27     ` Russell King - ARM Linux
2012-05-04 12:20   ` Arnd Bergmann
2012-05-04 16:39     ` Rob Herring
2012-05-04 16:56       ` Russell King - ARM Linux
2012-05-04 16:40         ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-04 16:51         ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-04 18:56       ` Arnd Bergmann
2012-05-03 14:18 ` Russell King - ARM Linux
2012-05-03 14:23   ` Magnus Damm
2012-05-03 16:27   ` Arnd Bergmann
2012-05-04  9:22   ` Arnaud Patard (Rtp)
2012-05-04 12:34     ` Arnd Bergmann
2012-05-10 10:55   ` Ben Dooks
2012-05-10 11:02     ` Russell King - ARM Linux
2012-05-03 14:46 ` Sascha Hauer
2012-05-04 16:24   ` Arnd Bergmann
2012-05-05  8:09     ` Sascha Hauer
2012-05-05 13:17       ` Arnd Bergmann
2012-05-14  8:54         ` Arnd Bergmann
2012-05-04  5:38 ` Deepak Saxena
2012-05-04  7:39   ` Russell King - ARM Linux
2012-05-04 14:20   ` Wookey
2012-05-04 14:35     ` Russell King - ARM Linux
2012-05-04 15:17       ` Arnd Bergmann
2012-05-04 16:05         ` Wookey
2012-05-04 18:49           ` Arnd Bergmann
2012-05-04 20:03       ` Linus Walleij
2012-05-04 20:42         ` Christian Robottom Reis
2012-05-04 21:05           ` Arnd Bergmann
2012-05-04 22:43         ` Russell King - ARM Linux [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=20120504224318.GL897@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).