From: Balaji T K <balajitk@ti.com>
To: "Kevyn-Alexandre Paré" <kevyn.alexandre.pare@gmail.com>
Cc: linux-mmc@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: OMAP35x MMC Host Controller compatibility with SDXC?
Date: Thu, 19 Sep 2013 20:01:13 +0530 [thread overview]
Message-ID: <523B0AB1.1050008@ti.com> (raw)
In-Reply-To: <CAL1yNcLxUnDCfZJxLVUjSDLtgvuBYEjL-pw_aZ8dA1rVu5o=4Q@mail.gmail.com>
On Wednesday 18 September 2013 02:32 AM, Kevyn-Alexandre Paré wrote:
> Hi,
>
> My question is related to the drivers/mmc/host/omap_hsmmc.c host
> controller compatibility with SDXC for the OMAP35x?
>
> Reading the TRM for OMAP35x:
> http://www.ti.com/lit/ug/spruf98x/spruf98x.pdf
>
> It's said that:
> - Full compliance with SD command/response sets as defined in the SD
> Memory Card Specifications, v2.0 including high-capacity SDHC cards up
> to 32GB.
>
> - Full compliance with sets as defined in the SD Card Specification,
> Part A2, SD Host Controller Standard Specification, v2.00
>
> It doesn't mention the SDXC?
> I'm trying to found my way through all the spec of sdcard.org.
>
> I'm still wondering why using SDXC of 64GB is working and doesn't pop
> a WARNING message and if it's safe??
>
> My test shows that I'm having some timeout in some cases (v3.4.60):
> omap_hsmmc omap_hsmmc.0: IRQ Status is 18000
> omap_hsmmc omap_hsmmc.0: MMC IRQ 0x18000 : ERRI CTO
> mmc0: req done (CMD52): -110: 00000000 00000000 00000000 00000000
> mmc0: starting CMD52 arg 80000c08 flags 00000195
>
> omap_hsmmc omap_hsmmc.0: mmc0: CMD5, argument 0x00000000
> omap_hsmmc omap_hsmmc.0: IRQ Status is 18000
> omap_hsmmc omap_hsmmc.0: MMC IRQ 0x18000 : ERRI CTO
> mmc0: req failed (CMD5): -110, retrying...
>
> mmc1: starting CMD8 arg 000001aa flags 000002f5
> omap_hsmmc omap_hsmmc.1: mmc1: CMD8, argument 0x000001aa
> mmc0: starting CMD18 arg 00020000 flags 000000b5
> omap_hsmmc omap_hsmmc.1: IRQ Status is 18000
> omap_hsmmc omap_hsmmc.1: MMC IRQ 0x18000 : ERRI CTO
> mmc1: req done (CMD8): -110: 00000000 00000000 00000000 00000000
>
> So CMD 52,5 and 8 gives me timeout...
For SD cards, these cmd's are expected to timeout during card initialization.
>
> Looking at the 3.11.1 there is 2 more validation for UHS that are not in 3.4.60:
> omap_hsmmc_set_clock // Enable High-Speed Support
> omap_set_bus_width
>
Those changes are not for SD3.0 speed modes
> Is it safe to use SDXC with OMAP35x or not? Should this pop a error message?
SDXC cards should work albeit at High Speed mode (as in SD2.0).
Refer to [1] for card size Vs speed mode/SD spec version.
Can you check if the filesystem type on SDXC card
is supported by the system software running on OMAP35x.
[1]
https://www.sdcard.org/consumers/speed/bus_speed/
>
> Best Regards,
>
> -KA
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-09-19 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 21:02 OMAP35x MMC Host Controller compatibility with SDXC? Kevyn-Alexandre Paré
2013-09-19 14:31 ` Balaji T K [this message]
2013-09-20 17:13 ` Kevyn-Alexandre Paré
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=523B0AB1.1050008@ti.com \
--to=balajitk@ti.com \
--cc=kevyn.alexandre.pare@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--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.