From: "Radek (Mrkva) Pilař" <mrkva@mrkva.eu>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] OMAP3 Touchbook: Fix MMC caps
Date: Thu, 24 Feb 2011 21:09:00 +0100 [thread overview]
Message-ID: <99a50271913b424eb17354f8b058c8dc@localhost> (raw)
In-Reply-To: <20110224193441.GF20560@atomide.com>
Well, MMC_CAP_8BIT data is definetely wrong - according to schematics,
there are only D0-D3 (+CLK and CMD) lines connected. I'm going to test 4
BIT and let you know.
On Thu, 24 Feb 2011 11:34:42 -0800, Tony Lindgren <tony@atomide.com>
wrote:
> * Radek (Mrkva) Pilař <mrkva@mrkva.eu> [110224 10:02]:
>> MMC controller cannot handle MMC_CAP_4_BIT_DATA nor
>> MMC_CAP_8_BIT_DATA - the card won't be detected (tested with two
>> SDHC cards, both Class6). Thus disabling.
>
> Hmm it might be worth checking that the MMC data lines are muxed
> correctly. Maybe make sure CONFIG_OMAP_MUX_DEBUG is set in
> your .config and CONFIG_DEBUG_FS too. Then boot and and mount
> debugfs with mount -tdebugfs debugfs /sys/kernel/debug.
> Then you can do:
>
> # grep -i mmc1 /sys/kernel/debug/omap_mux/* | grep dat
>
> And check the settings. Changing the values could cause data
> corruption, so use a temporary root file system!
>
> Tony
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-02-24 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 17:59 [PATCH 1/2] OMAP3 Touchbook: Fix MMC caps Radek (Mrkva) Pilař
2011-02-24 19:34 ` Tony Lindgren
2011-02-24 20:09 ` Radek (Mrkva) Pilař [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=99a50271913b424eb17354f8b058c8dc@localhost \
--to=mrkva@mrkva.eu \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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