From: Tony Lindgren <tony@atomide.com>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-omap@vger.kernel.org
Subject: [PATCH 0/6] omap: Board specific muxing using hwmod
Date: Thu, 02 Dec 2010 16:45:14 -0800 [thread overview]
Message-ID: <20101203004040.31687.9476.stgit@baageli.muru.com> (raw)
Hi all,
Here are some patches to allow us to pass the board specific mux data
to the platform level device init code, and then allow hwmod state
changes to do the pin muxing.
Dynamic remuxing is also supported as needed, the last patch in this
series sets up the board-*.c data for n8x0 to do uart3 rx pin remuxing
for the idle modes.
Regards,
Tony
---
Tony Lindgren (6):
omap2+: Add omap_mux_get_by_name
omap2+: Add support for hwmod specific muxing of devices
omap2+: Allow hwmod state changes to mux pads based on the state changes
omap2+: Add struct omap_device_board_data and allow omap_device_build initialize pads to mux
omap2+: Use omap_device_board_data for platform level serial init
omap2+: Initialize serial ports for wake-up events for n8x0
arch/arm/mach-omap2/board-n8x0.c | 66 ++++++++-
arch/arm/mach-omap2/devices.c | 2
arch/arm/mach-omap2/gpio.c | 2
arch/arm/mach-omap2/mux.c | 188 ++++++++++++++++++++++---
arch/arm/mach-omap2/mux.h | 39 +++++
arch/arm/mach-omap2/omap_hwmod.c | 14 +-
arch/arm/mach-omap2/pm.c | 3
arch/arm/mach-omap2/serial.c | 29 +++-
arch/arm/plat-omap/i2c.c | 4 -
arch/arm/plat-omap/include/plat/omap_device.h | 19 ++-
arch/arm/plat-omap/include/plat/omap_hwmod.h | 32 ++++
arch/arm/plat-omap/include/plat/serial.h | 5 +
arch/arm/plat-omap/omap_device.c | 14 ++
13 files changed, 366 insertions(+), 51 deletions(-)
--
Signature
next reply other threads:[~2010-12-03 0:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 0:45 Tony Lindgren [this message]
2010-12-03 0:45 ` [PATCH 1/6] omap2+: Add omap_mux_get_by_name Tony Lindgren
2010-12-03 0:45 ` [PATCH 2/6] omap2+: Add support for hwmod specific muxing of devices Tony Lindgren
2010-12-23 2:46 ` Tony Lindgren
2010-12-03 0:45 ` [PATCH 3/6] omap2+: Allow hwmod state changes to mux pads based on the state changes Tony Lindgren
2010-12-23 2:48 ` Tony Lindgren
2010-12-03 0:45 ` [PATCH 4/6] omap2+: Add struct omap_device_board_data and allow omap_device_build initialize pads to mux Tony Lindgren
2010-12-23 2:49 ` Tony Lindgren
2010-12-03 0:45 ` [PATCH 5/6] omap2+: Use omap_device_board_data for platform level serial init Tony Lindgren
2010-12-23 2:51 ` Tony Lindgren
2010-12-03 0:45 ` [PATCH 6/6] omap2+: Initialize serial ports for wake-up events for n8x0 Tony Lindgren
2010-12-14 3:17 ` Kevin Hilman
2010-12-18 17:53 ` Tony Lindgren
2010-12-23 2:53 ` Tony Lindgren
2010-12-21 17:04 ` [PATCH 0/6] omap: Board specific muxing using hwmod Paul Walmsley
2010-12-23 3:07 ` Tony Lindgren
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=20101203004040.31687.9476.stgit@baageli.muru.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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).