From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] ARM: OMAP2+: hsmmc: Let board files specify if an external transceiver exists
Date: Fri, 9 Mar 2012 14:41:48 +0530 [thread overview]
Message-ID: <1331284309-22101-4-git-send-email-rnayak@ti.com> (raw)
In-Reply-To: <1331284309-22101-1-git-send-email-rnayak@ti.com>
The omap2_hsmmc_info structure provides a way for board files to specify
if an external transciever exists for the mmc module. So get rid of the
assumption based on external clock.
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
Cc: Balaji TK <balajitk@ti.com>
Cc: Venkatraman S <svenkatr@ti.com>
---
arch/arm/mach-omap2/hsmmc.c | 2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-omap2/hsmmc.c b/arch/arm/mach-omap2/hsmmc.c
index 0133b29..0aa4587 100644
--- a/arch/arm/mach-omap2/hsmmc.c
+++ b/arch/arm/mach-omap2/hsmmc.c
@@ -387,8 +387,6 @@ static int omap_hsmmc_pdata_init(struct omap2_hsmmc_info *c,
mmc->select_input_clk_src = hsmmc1_select_input_clk_src;
break;
case 2:
- if (c->ext_clock)
- c->transceiver = 1;
if (c->transceiver && (c->caps & MMC_CAP_8_BIT_DATA)) {
c->caps &= ~MMC_CAP_8_BIT_DATA;
c->caps |= MMC_CAP_4_BIT_DATA;
--
1.7.1
next prev parent 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 [PATCH 0/4] hsmmc cleanups in platform callback routines Rajendra Nayak
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 ` Rajendra Nayak [this message]
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-4-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).