linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] ARM: OMAP2430SDP: No support to switch to external clock on omap2430
Date: Fri, 9 Mar 2012 14:41:49 +0530	[thread overview]
Message-ID: <1331284309-22101-5-git-send-email-rnayak@ti.com> (raw)
In-Reply-To: <1331284309-22101-1-git-send-email-rnayak@ti.com>

As stated in the latest 2430 TRM version Z, Table 7-135 and Table 7-154,
omap2430 does not support switching between internal loopback and external
clock for MMC modules. This is supported only on some instances of MMC
modules on omap3430 only.

Signed-off-by: Rajendra Nayak <rnayak@ti.com>
Cc: Balaji TK <balajitk@ti.com>
Cc: Venkatraman S <svenkatr@ti.com>
---
 arch/arm/mach-omap2/board-2430sdp.c |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/arch/arm/mach-omap2/board-2430sdp.c b/arch/arm/mach-omap2/board-2430sdp.c
index 7370983..eb70b00 100644
--- a/arch/arm/mach-omap2/board-2430sdp.c
+++ b/arch/arm/mach-omap2/board-2430sdp.c
@@ -249,7 +249,6 @@ static struct omap2_hsmmc_info mmc[] __initdata = {
 		.caps		= MMC_CAP_4_BIT_DATA,
 		.gpio_cd	= -EINVAL,
 		.gpio_wp	= -EINVAL,
-		.ext_clock	= 1,
 	},
 	{}	/* Terminator */
 };
-- 
1.7.1

      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 ` [PATCH 3/4] ARM: OMAP2+: hsmmc: Let board files specify if an external transceiver exists Rajendra Nayak
2012-03-09  9:11 ` Rajendra Nayak [this message]

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-5-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).