linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [RFC] pinctrl: add a driver for Energy Micro's efm32 SoCs
Date: Fri, 9 Dec 2011 13:55:16 +0000	[thread overview]
Message-ID: <201112091355.16720.arnd@arndb.de> (raw)
In-Reply-To: <20111209092300.GR4585@pengutronix.de>

On Friday 09 December 2011, Uwe Kleine-K?nig wrote:
> On Thu, Dec 08, 2011 at 11:55:53PM +0100, Arnd Bergmann wrote:
> > On Thursday 08 December 2011 23:40:57 Uwe Kleine-K?nig wrote:
> > > Signed-off-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
> > > ---
> > > Note that there is no support yet for efm32 in mainline, so ARCH_EFM32
> > > isn't defined.
> > 
> > Since the platform is not yet part of the architecture, it will have
> > to use device tree based probing when it gets added. I would suggest
> > only merging drivers for it that can deal with this and do not rely
> > on platform_data.
>
> I feared you will say that. These machines have at most 4MiB of RAM.
> I'll have to evaluate if dt is too heavy for them.

What's the state of the platform code? Is this based on Catalin's
Cortex-M3 tree? I've heard a few people express interest in getting
various M3 based SoCs supported mainline and I think that would
be a good idea, but I would also expect that device tree is one
of the lesser problems here.

	Arnd

  reply	other threads:[~2011-12-09 13:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-08 22:40 [PATCH] [RFC] pinctrl: add a driver for Energy Micro's efm32 SoCs Uwe Kleine-König
2011-12-08 22:55 ` Arnd Bergmann
2011-12-09  9:23   ` Uwe Kleine-König
2011-12-09 13:55     ` Arnd Bergmann [this message]
2011-12-09 14:15       ` Uwe Kleine-König
2011-12-08 23:14 ` Stephen Warren
2011-12-09  1:01   ` Shawn Guo
2011-12-09  3:44     ` Stephen Warren
2011-12-09  4:32       ` Shawn Guo
2011-12-09  4:47         ` Stephen Warren
2011-12-09  5:14           ` Shawn Guo
2011-12-09 11:08             ` Sascha Hauer
2011-12-09 13:01               ` Uwe Kleine-König
2011-12-10  0:18               ` Linus Walleij
2011-12-12 14:37                 ` Sascha Hauer
2011-12-12 15:29                   ` Uwe Kleine-König
2011-12-13  0:41                   ` Linus Walleij
2011-12-09 16:53             ` Stephen Warren
2011-12-09 15:03           ` Dong Aisheng
2011-12-09 16:49             ` Stephen Warren
2011-12-09 17:24               ` Tony Lindgren
2011-12-09 17:53                 ` Tony Lindgren
2011-12-10  0:14                   ` Stephen Warren
2011-12-11 19:34                     ` Tony Lindgren
2011-12-09  9:31   ` Uwe Kleine-König
2011-12-10  0:04   ` Linus Walleij

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=201112091355.16720.arnd@arndb.de \
    --to=arnd@arndb.de \
    --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).