From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/4] pinctrl: add a driver for NVIDIA Tegra
Date: Thu, 2 Feb 2012 14:26:54 +0100 [thread overview]
Message-ID: <CACRpkda+KCutSFgPwH2Xvd14h0OCrArFGXAidp3n_ZgG28KB5g@mail.gmail.com> (raw)
In-Reply-To: <1328130290-17607-1-git-send-email-swarren@nvidia.com>
On Wed, Feb 1, 2012 at 10:04 PM, Stephen Warren <swarren@nvidia.com> wrote:
> This adds a driver for the Tegra pinmux, and required parameterization
> data for Tegra20 and Tegra30.
OK so I've applied this monster patch and the three others,
the diffstat looks like so:
git diff --stat v3.3-rc2..HEAD
arch/arm/mach-tegra/Kconfig | 4 +
arch/arm/mach-tegra/Makefile | 3 -
arch/arm/mach-tegra/board-harmony-pinmux.c | 362 ++-
arch/arm/mach-tegra/board-paz00-pinmux.c | 362 ++-
arch/arm/mach-tegra/board-pinmux.c | 62 +-
arch/arm/mach-tegra/board-pinmux.h | 39 +-
arch/arm/mach-tegra/board-seaboard-pinmux.c | 442 ++-
arch/arm/mach-tegra/board-trimslice-pinmux.c | 366 ++-
arch/arm/mach-tegra/include/mach/pinconf-tegra.h | 63 +
arch/arm/mach-tegra/include/mach/pinmux-tegra20.h | 184 -
arch/arm/mach-tegra/include/mach/pinmux-tegra30.h | 320 --
arch/arm/mach-tegra/include/mach/pinmux.h | 302 --
arch/arm/mach-tegra/pinmux-tegra20-tables.c | 244 --
arch/arm/mach-tegra/pinmux-tegra30-tables.c | 376 ---
arch/arm/mach-tegra/pinmux.c | 987 ------
drivers/pinctrl/Kconfig | 15 +
drivers/pinctrl/Makefile | 3 +
drivers/pinctrl/pinctrl-tegra.c | 559 +++
drivers/pinctrl/pinctrl-tegra.h | 163 +
drivers/pinctrl/pinctrl-tegra20.c | 2860 ++++++++++++++++
drivers/pinctrl/pinctrl-tegra30.c | 3726 +++++++++++++++++++++
21 files changed, 8482 insertions(+), 2960 deletions(-)
It's still pretty big, adding some 6000 lines in sum total, but you've made
your case for having all information about the hardware in the driver
quite clear so I've not got much more to say. Short story: the driver knows
all about what the hardware can do, and the platform data or device
tree will decide how these capabilities are employed on a certain
system.
What is nice is to have this out of the ARM tree and under pinctrl
subsystem control.
Olof, Arnd: please verify that this is a direction you accept for the Tegra.
(Olof has already ACK:ed it, mainly thinking about Arnd.)
I've created a separate branch named pinctrl-tegra-for-next for this
series and merged it into my devel and for-next branches and pushed.
As suggested by Olof devel and for-next may be rebased but the
tegra branch will stay intact (fixes on top is OK).
Olof: I've published the pinctrl-tegra-for-next branch based on v3.3-rc2
here:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
pinctrl-tegra-for-next
Yours,
Linus Walleij
next prev parent reply other threads:[~2012-02-02 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1328130290-17607-1-git-send-email-swarren@nvidia.com>
2012-02-01 21:04 ` [PATCH V2 2/4] ARM: tegra: Select PINCTRL Kconfig variables Stephen Warren
2012-02-01 21:04 ` [PATCH V2 4/4] ARM: tegra: Remove pre-pinctrl pinmux driver Stephen Warren
2012-02-02 13:26 ` Linus Walleij [this message]
2012-02-02 14:43 ` [PATCH V2 1/4] pinctrl: add a driver for NVIDIA Tegra Shawn Guo
2012-02-02 15:33 ` Arnd Bergmann
2012-02-03 14:57 ` Linus Walleij
2012-02-03 17:50 ` Stephen Warren
2012-02-03 21:44 ` Linus Walleij
2012-02-03 17:58 ` Tony Lindgren
2012-02-03 18:55 ` Arnd Bergmann
2012-02-03 22:12 ` 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=CACRpkda+KCutSFgPwH2Xvd14h0OCrArFGXAidp3n_ZgG28KB5g@mail.gmail.com \
--to=linus.walleij@linaro.org \
--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).