From: Arnd Bergmann <arnd@arndb.de>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Dave Jones <davej@redhat.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Tony Lindgren <tony@atomide.com>,
Linus Walleij <linus.walleij@linaro.org>,
cpufreq@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-arm-kernel@lists.infradead.org
Subject: Re: Status of arch/arm in linux-next
Date: Tue, 26 Apr 2011 16:05:26 +0200 [thread overview]
Message-ID: <201104261605.26791.arnd@arndb.de> (raw)
In-Reply-To: <alpine.LFD.2.00.1104211629300.24613@xanadu.home>
On Thursday 21 April 2011, Nicolas Pitre wrote:
> > if there's commonality between some of the ARM arch drivers, why can't
> > there be a arch/arm/cpufreq/ dir for the shared code, and do everything there ?
>
> Because usually there isn't. "ARM" is just a CPU architecture, not a
> system architecture. Everything around the core is different from one
> vendor to the next. And when commonality exists it is much easier to
> deal with if it is close together.
Exactly. To make matters worse, we are starting to see a number of vendors
that use multiple CPU architectures with the same I/O devices (e.g. Renesas,
Freescale, Xilinx, TI, ...). Not sure if any of these use the same cpufreq
register on more than one architecture, but it's quite likely to happen
at some point.
Arnd
next prev parent reply other threads:[~2011-04-26 14:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110414094447.GA1611@n2100.arm.linux.org.uk>
[not found] ` <201104191655.13133.arnd@arndb.de>
[not found] ` <BANLkTi=kGxL9N-RNqxmeqs4zeYo0zzfmhQ@mail.gmail.com>
2011-04-19 16:01 ` Status of arch/arm in linux-next Arnd Bergmann
2011-04-19 16:05 ` Mark Brown
2011-04-21 20:14 ` Dave Jones
2011-04-21 21:02 ` Nicolas Pitre
2011-04-22 7:17 ` Tony Lindgren
2011-04-26 14:05 ` Arnd Bergmann [this message]
2011-04-26 17:04 ` Rafael J. Wysocki
2011-04-26 18:15 ` Dave Jones
2011-04-29 20:15 ` Dave Jones
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 17:01 ` Jonathan Nieder
2011-08-14 17:17 ` Kay Sievers
2011-05-01 23:02 ` Status of arch/arm in linux-next Jamie Lokier
2011-04-19 16:27 ` Dave Jones
2011-04-19 17:12 ` Arnd Bergmann
2011-04-20 6:36 ` 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=201104261605.26791.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=nicolas.pitre@linaro.org \
--cc=rjw@sisk.pl \
--cc=tony@atomide.com \
/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