public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>
To: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Andrew\"" <andrew.chih.howe.khor@intel.com>, kok.howg.ewe@intel.com
Subject: A MMC card transfer issue
Date: Tue, 09 Nov 2010 14:39:40 +0900	[thread overview]
Message-ID: <4CD8DE9C.4040505@dsn.okisemi.com> (raw)

I am facing the issue about some MMC cards on Intel EG20T PCH (Platform Controller Hub).
The linux version is 2.6.36.
I can not transfer data the MMC cards (e.g. Transcned MMC card).
The card is 1 bit bus width. And the card is according to MMC specification V3.x.
And the EG20T has a 4 bit bus width capability 
Linux MMC standard driver decides the card bus width as 4 bit,
if the MMC specification version is larger than or equal to V4.0 like below.

linux/drivers/mmc/core/mmc.c

 505        /*
 506         * Activate wide bus (if supported).
 507         */
 508        if ((card->csd.mmca_vsn >= CSD_SPEC_VER_4) &&
 509            (host->caps & (MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA))) {
 510                unsigned ext_csd_bit, bus_width;
 511
 512                if (host->caps & MMC_CAP_8_BIT_DATA) {
 513                        ext_csd_bit = EXT_CSD_BUS_WIDTH_8;
 514                        bus_width = MMC_BUS_WIDTH_8;
 515                } else {
 516                        ext_csd_bit = EXT_CSD_BUS_WIDTH_4;
 517                        bus_width = MMC_BUS_WIDTH_4;
 518                }
 519
 520                err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
 521                                 EXT_CSD_BUS_WIDTH, ext_csd_bit);
 522
 523                if (err && err != -EBADMSG)
 524                        goto free_card;
 525
 526                if (err) {
 527                        printk(KERN_WARNING "%s: switch to bus width %d "
 528                               "failed\n", mmc_hostname(card->host),
 529                               1 << bus_width);
 530                        err = 0;
 531                } else {
 532                        mmc_set_bus_width(card->host, bus_width);
 533                }
 534        }
 535

However the MMC specification version id is the same as V3.x and V4.0.
Therefore the driver uses the 4 bit bus width for the MMC card 
even if the card has only 1 bit bus width.
I modified the driver to use 1 bit bus width only tentatively and confirmed that
we can mount the card and R/W correctly.

I think we can not support MMC_CAP_4_BIT_DATA or MMC_CAP_8_BIT_DATA in MMC V4.0.

How do you think ?

-- 
Thanks,
Tomoya MORINAGA(OKI SEMICONDUCTOR CO., LTD.)

             reply	other threads:[~2010-11-09  5:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09  5:39 Tomoya MORINAGA [this message]
2010-11-09  5:53 ` A MMC card transfer issue Kyungmin Park
2010-11-09  7:29   ` Tomoya MORINAGA
2010-11-11  2:59   ` Tomoya MORINAGA
2010-12-01  1:08     ` Tomoya MORINAGA
     [not found]       ` <2D50F985-2383-4406-8514-DFE462A5F546@marvell.com>
     [not found]         ` <4D2E0464ABB54FFF9C10583336E27879@hacdom.okisemi.com>
2011-01-19  0:59           ` Philip Rakity
2011-01-19  1:29             ` Tomoya MORINAGA
2011-01-19  1:41               ` Chris Ball
2011-01-19  3:12                 ` Philip Rakity
2011-01-19  6:05           ` Philip Rakity
2011-01-19  6:30             ` Tomoya MORINAGA
2011-01-19 17:42             ` Chris Ball
2011-01-19 23:49               ` Tomoya MORINAGA
2011-01-26  8:28               ` Tomoya MORINAGA
2011-01-26 15:42                 ` Philip Rakity
2011-01-27  1:00                   ` Tomoya MORINAGA
2011-01-27  1:03                     ` Philip Rakity
2011-01-27  1:31                       ` Tomoya MORINAGA
2011-01-27  1:43                         ` Philip Rakity
2011-01-27  3:20                           ` Tomoya MORINAGA

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=4CD8DE9C.4040505@dsn.okisemi.com \
    --to=tomoya-linux@dsn.okisemi.com \
    --cc=andrew.chih.howe.khor@intel.com \
    --cc=kok.howg.ewe@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox