From: Mike Rapoport <mike@compulab.co.il>
To: linux-omap@vger.kernel.org
Cc: Mike Rapoport <mike@compulab.co.il>
Subject: [RFC PATCH 0/3] mux framework rework
Date: Wed, 28 Oct 2009 15:07:42 +0200 [thread overview]
Message-ID: <cover.1256734115.git.mike@compulab.co.il> (raw)
This is an attempt to start rework of the mux framework keeping as
much backward compatibility as possible.
The patch serie introduces a new mux configuration interface that
follows the ideas of PXA MFP implementation ([1] and [2]).
The mux configuration interface is implemented for OMAP3 and partially
for OMAP2 processors.
The OMAP2 implementation is far from being complete. Unfortunately I
do not have OMAP2 docs, so I've added only configration for pins
defined in omap24xx_pins table.
The older opam_cfg_reg interface is still present and can be used to
avoid too many broken things in steps 2 & 3 as of Tony's plans ([3]).
[1] Documentation/arm/pxa/mfp.txt
[2] http://elinux.org/OMAP_wishlist#References
[3] http://elinux.org/OMAP_wishlist#Initial_plans_.28from_Tony.2C_for_next_merge_window.29
Changes since commit 0bbf5337f2f2957775051a3caf60b66d3306c815
Tony Lindgren
Fix compile for 1510 innovator
Mike Rapoport (3):
omap2: mux: intoduce omap_mux_{read,write}
omap: mux: add interface for encoded mux configration
omap2: mux: implement encoded mux configuration
arch/arm/mach-omap2/include/mach/mux.h | 452 +++++++++++++++
arch/arm/mach-omap2/include/mach/mux24xx.h | 128 ++++
arch/arm/mach-omap2/include/mach/mux34xx.h | 862 ++++++++++++++++++++++++++++
arch/arm/mach-omap2/mux.c | 158 +++++-
arch/arm/plat-omap/include/plat/mux.h | 62 +--
arch/arm/plat-omap/mux.c | 17 +
6 files changed, 1614 insertions(+), 65 deletions(-)
create mode 100644 arch/arm/mach-omap2/include/mach/mux.h
create mode 100644 arch/arm/mach-omap2/include/mach/mux24xx.h
create mode 100644 arch/arm/mach-omap2/include/mach/mux34xx.h
next reply other threads:[~2009-10-28 13:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 13:07 Mike Rapoport [this message]
2009-10-28 13:07 ` [PATCH 1/3] omap2: mux: intoduce omap_mux_{read,write} Mike Rapoport
2009-10-29 15:50 ` Tony Lindgren
2009-10-29 16:51 ` [PATCH 1/3] omap2: mux: intoduce omap_mux_{read,write}, v2 Tony Lindgren
2009-10-29 20:28 ` Mike Rapoport
2009-10-29 20:30 ` Tony Lindgren
2009-10-28 13:07 ` [PATCH 2/3] omap: mux: add interface for encoded mux configration Mike Rapoport
2009-10-28 13:07 ` [PATCH 3/3] omap2: mux: implement encoded mux configuration Mike Rapoport
2009-10-28 16:53 ` [RFC PATCH 0/3] mux framework rework Tony Lindgren
2009-10-29 9:46 ` Mike Rapoport
2009-10-29 15:43 ` 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=cover.1256734115.git.mike@compulab.co.il \
--to=mike@compulab.co.il \
--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 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.