From: swarren@nvidia.com (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] arm/tegra: Convert gpio & pinmux to platform devices
Date: Thu, 22 Sep 2011 15:06:03 -0600 [thread overview]
Message-ID: <1316725567-17881-1-git-send-email-swarren@nvidia.com> (raw)
This series converts the Tegra GPIO and pinmux drivers to be regular
platform devices.
The series is extracted from an earlier series I posted that augmented
these drivers to initialize HW state from the device-tree. I'm holding
off on that aspect of the changes, since it's not entirely clear to me
whether the new pinmux API should drive the initial pinmux state setup
via "system hog" definitions, or whether pinmux drivers should indeed
do their own thing.
Dependencies:
* The patches need to be merged in one branch in order for bisectability.
* At least patch 3 depends on changes in Russell's gpio branch, since it
edits a file renamed there. I imagine the series will be merged into
that branch.
* The whole series is based off next-20110922 plus a couple patches in the
ARM patch system (7094, 7095).
* This series affects both the GPIO and pinmux drivers. Potentially, the
changes to the two driver could be split into separate series, but this
would be complicated by the fact patch 1 edits all the board files to
make the same change for both GPIO and pinmux; if split up, merging that
all back together would cause conflicts.
* Patch 1's changes to board-seaboard-pinmux.c will have some merge
conflicts with the patches Peter De Schrijver recently posted to enhance
that file to support Ventana; each of our patches will change the context
changes in the others' diffs. I'm not sure how best to manage this.
Stephen Warren (4):
arm/tegra: Prep boards for gpio/pinmux conversion to pdevs
arm/dt: Tegra: Add pinmux node to tegra20.dtsi
gpio/tegra: Convert to a platform device
arm/tegra: Convert pinmux driver to a platform device
.../devicetree/bindings/pinmux/pinmux_nvidia.txt | 5 +++
arch/arm/boot/dts/tegra20.dtsi | 5 +++
arch/arm/mach-tegra/board-harmony-pinmux.c | 8 +++++
arch/arm/mach-tegra/board-paz00-pinmux.c | 8 +++++
arch/arm/mach-tegra/board-seaboard-pinmux.c | 9 ++++-
arch/arm/mach-tegra/board-trimslice-pinmux.c | 7 ++++
arch/arm/mach-tegra/devices.c | 10 ++++++
arch/arm/mach-tegra/devices.h | 2 +
arch/arm/mach-tegra/pinmux.c | 26 ++++++++++++++++
drivers/gpio/gpio-tegra.c | 31 +++++++++++++-------
10 files changed, 98 insertions(+), 13 deletions(-)
create mode 100644 Documentation/devicetree/bindings/pinmux/pinmux_nvidia.txt
next reply other threads:[~2011-09-22 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 21:06 Stephen Warren [this message]
2011-09-22 21:06 ` [PATCH 1/4] arm/tegra: Prep boards for gpio/pinmux conversion to pdevs Stephen Warren
2011-09-22 21:06 ` [PATCH 2/4] arm/dt: Tegra: Add pinmux node to tegra20.dtsi Stephen Warren
2011-09-22 21:06 ` [PATCH 3/4] gpio/tegra: Convert to a platform device Stephen Warren
2011-09-22 21:06 ` [PATCH 4/4] arm/tegra: Convert pinmux driver " Stephen Warren
2011-09-23 16:48 ` [PATCH 0/4] arm/tegra: Convert gpio & pinmux to platform devices Arnd Bergmann
2011-09-28 3:56 ` Stephen Warren
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=1316725567-17881-1-git-send-email-swarren@nvidia.com \
--to=swarren@nvidia.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 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).