From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Status of arch/arm in linux-next
Date: Fri, 15 Apr 2011 09:26:43 +0300 [thread overview]
Message-ID: <20110415062643.GB12272@atomide.com> (raw)
In-Reply-To: <BANLkTikVfdVQuR_nJZnra7Bo=CQgOfS5Zg@mail.gmail.com>
* Linus Walleij <linus.walleij@linaro.org> [110415 04:14]:
> 2011/4/14 Russell King - ARM Linux <linux@arm.linux.org.uk>:
>
> > This morning, I looked at linux-next to find out how arch/arm is doing
> > for the next merge window.
> >
> > $ git diff -C --cumulative v2.6.39-rc1... arch/arm
> > (...)
> > ? 7.6% arch/arm/mach-ux500/include/mach/
> > ?46.1% arch/arm/mach-ux500/
> > (...)
> > Please take a moment to consider how Linus will react to this at the
> > next merge window.
>
> This instance of Linus feels guilty for that...
>
> Since ~50% of it is ux500 that I usually merge through your tree,
> I suspect you're simply not going to pull it so then half of the problem
> is gone already :-D
>
> Anyway, the bulk of that is a PRCMU driver, similar to the stuff
> in arch/arm/mach-omap2/prcm*. So let's think about what we can
> do about it.
Yeah OK.
> Since this is a one-off kind of thing, a singleton driver that controls
> power, reset and some GPIO on the chip. I contemplate moving the
> stuff to either:
>
> drivers/misc/ux500/*
> include/linux/misc/ux500/*
>
> or:
>
> drivers/platform/arm/ux500/*
> include/linux/platform/arm/ux500/*
>
> Are any of these generally speaking good ideas?
Or maybe drivers/arm?
Anyways, whatever can be done as loadable modules should be done
that way. That makes the life for distros much easier ;)
> Either place outside arch/arm/* is fine with me, creating something like
> drivers/prcmu/* would be a bit thick since the hardware basically does
> not look like anything else.
>
> The basic problem it's reflecting is that ARM does not have something
> like ACPI, that's basically what the driver is doing, and since every
> vendor does their own HW thingy it's not like it's easily consolidated.
Yeah and that's going to take time.
> In the meantime I'm working on migrating GPIO drivers from mach-u300
> and plat-nomadik into drivers/gpio so I will hopefully provide some negative
> stats.
We too can move the omap gpio code there too..
Regards,
Tony
next prev parent reply other threads:[~2011-04-15 6:26 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 9:44 Status of arch/arm in linux-next Russell King - ARM Linux
2011-04-14 11:08 ` Tony Lindgren
2011-04-14 12:02 ` Russell King - ARM Linux
2011-04-14 12:31 ` Tony Lindgren
2011-04-14 14:20 ` Mark Brown
2011-04-14 14:26 ` Tony Lindgren
2011-04-14 14:31 ` Russell King - ARM Linux
2011-04-14 18:32 ` Mark Brown
2011-04-15 15:12 ` Grant Likely
2011-04-15 15:56 ` Russell King - ARM Linux
2011-04-15 16:10 ` Grant Likely
2011-04-16 8:28 ` Russell King - ARM Linux
2011-04-16 16:57 ` Mark Brown
2011-04-18 8:10 ` Tony Lindgren
2011-04-18 13:57 ` Mark Brown
2011-04-18 14:41 ` Tony Lindgren
2011-04-18 14:41 ` Tony Lindgren
2011-04-18 15:58 ` Mark Brown
2011-04-18 15:58 ` Mark Brown
2011-04-18 17:18 ` Russell King - ARM Linux
2011-04-18 20:23 ` Mark Brown
2011-04-18 21:40 ` Thomas Gleixner
2011-04-18 23:55 ` Mark Brown
2011-04-14 14:07 ` Mark Brown
2011-04-15 2:59 ` Nico Erfurth
2011-04-15 8:21 ` Nicolas Ferre
2011-04-15 13:13 ` Nico Erfurth
2011-04-15 1:16 ` Linus Walleij
2011-04-15 6:26 ` Tony Lindgren [this message]
2011-04-19 14:16 ` Arnd Bergmann
2011-04-19 14:50 ` Mark Brown
2011-04-19 14:55 ` Arnd Bergmann
2011-04-19 15:04 ` Mark Brown
2011-04-19 15:14 ` Linus Walleij
2011-04-19 16:01 ` Arnd Bergmann
2011-04-19 16:01 ` Arnd Bergmann
2011-04-19 16:05 ` Mark Brown
2011-04-19 16:05 ` Mark Brown
2011-04-21 20:14 ` Dave Jones
2011-04-21 20:14 ` Dave Jones
2011-04-21 21:02 ` Nicolas Pitre
2011-04-21 21:02 ` Nicolas Pitre
2011-04-22 7:17 ` Tony Lindgren
2011-04-22 7:17 ` Tony Lindgren
2011-04-26 14:05 ` Arnd Bergmann
2011-04-26 14:05 ` Arnd Bergmann
2011-04-26 17:04 ` Rafael J. Wysocki
2011-04-26 17:04 ` Rafael J. Wysocki
2011-04-26 18:15 ` Dave Jones
2011-04-26 18:15 ` Dave Jones
2011-04-29 20:15 ` Dave Jones
2011-04-29 20:15 ` Dave Jones
2011-04-30 0:05 ` Nicolas Pitre
2011-04-30 0:05 ` Nicolas Pitre
2011-08-13 15:46 ` [BUG?] Moving drivers to drivers/cpufreq/ causes all to be loaded Jonathan Nieder
2011-08-13 19:02 ` Jonathan Nieder
2011-08-13 21:11 ` Dave Jones
2011-08-14 0:18 ` Mattia Dongili
2011-08-14 0:18 ` Mattia Dongili
2011-08-14 17:01 ` Jonathan Nieder
2011-08-14 17:17 ` Kay Sievers
2011-08-14 17:17 ` Kay Sievers
2011-05-01 23:02 ` Status of arch/arm in linux-next Jamie Lokier
2011-05-01 23:02 ` Jamie Lokier
2011-04-19 16:27 ` Dave Jones
2011-04-19 16:27 ` Dave Jones
2011-04-19 17:12 ` Arnd Bergmann
2011-04-19 17:12 ` Arnd Bergmann
2011-04-20 6:36 ` Linus Walleij
2011-04-20 6:36 ` Linus Walleij
2011-04-21 7:32 ` Linus Walleij
2011-04-21 8:25 ` Arnd Bergmann
2011-04-22 7:56 ` Linus Walleij
2011-04-22 11:46 ` Linus Walleij
2011-05-02 13:49 ` Samuel Ortiz
2011-05-02 19:21 ` Linus Walleij
2011-04-20 7:33 ` Tony Lindgren
2011-04-20 7:43 ` Arnd Bergmann
2011-04-15 14:30 ` Martin Guy
2011-04-15 15:50 ` Russell King - ARM Linux
2011-04-18 15:17 ` Alexey Zaytsev
2011-04-18 16:23 ` Linus Torvalds
2011-04-18 21:54 ` Alexey Zaytsev
2011-04-19 15:02 ` Linus Torvalds
2011-04-19 15:20 ` Jean-Christophe PLAGNIOL-VILLARD
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=20110415062643.GB12272@atomide.com \
--to=tony@atomide.com \
--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.