From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] hsmmc cleanups in platform callback routines
Date: Fri, 9 Mar 2012 14:41:45 +0530 [thread overview]
Message-ID: <1331284309-22101-1-git-send-email-rnayak@ti.com> (raw)
This series mainly splits the platform callbacks implemented in
hsmmc.c (for clk source selection and pbiascell programming)
rather than doing everything in a single callback which
is what is done today. This cleanup is ground work before all these
callbacks are moved into hsmmc/system-control module driver
out of machine folder.
Patches tested on omap3 beagle-Xm and omap4 panda boards.
regards,
Rajendra
Rajendra Nayak (4):
ARM: OMAP2+: hsmmc: Add a flag to identify modules supporting clock
src selection
ARM: OMAP2+: hsmmc: Split the clock src selection and pbias
programming
ARM: OMAP2+: hsmmc: Let board files specify if an external
transceiver exists
ARM: OMAP2430SDP: No support to switch to external clock on omap2430
arch/arm/mach-omap2/board-2430sdp.c | 1 -
arch/arm/mach-omap2/hsmmc.c | 101 ++++++++++++----------------
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 14 +++-
arch/arm/plat-omap/include/plat/mmc.h | 2 +
drivers/mmc/host/omap_hsmmc.c | 3 +
5 files changed, 58 insertions(+), 63 deletions(-)
next reply other threads:[~2012-03-09 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 9:11 Rajendra Nayak [this message]
2012-03-09 9:11 ` [PATCH 1/4] ARM: OMAP2+: hsmmc: Add a flag to identify modules supporting clock src selection Rajendra Nayak
2012-03-09 9:11 ` [PATCH 2/4] ARM: OMAP2+: hsmmc: Split the clock src selection and pbias programming Rajendra Nayak
2012-03-09 9:11 ` [PATCH 3/4] ARM: OMAP2+: hsmmc: Let board files specify if an external transceiver exists Rajendra Nayak
2012-03-09 9:11 ` [PATCH 4/4] ARM: OMAP2430SDP: No support to switch to external clock on omap2430 Rajendra Nayak
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=1331284309-22101-1-git-send-email-rnayak@ti.com \
--to=rnayak@ti.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).