From: Jaehoon Chung <jh80.chung@samsung.com>
To: Jean-Michel Hautbois <jean-michel.hautbois@vodalys.com>,
Hsin-Hsiang Tseng <hsinhsiangtseng@gmail.com>
Cc: Fabio Estevam <festevam@gmail.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: Sandisk MMC I/O errors
Date: Wed, 06 Aug 2014 20:44:21 +0900 [thread overview]
Message-ID: <53E21515.3060807@samsung.com> (raw)
In-Reply-To: <CAL8zT=gS1rwFU1eUcYNpKmygpnmTDXeQRtg6Uxr9FVXRJ6PmeA@mail.gmail.com>
Hi,
In my case, -84 error is related with timing.
I recommend to check your clock source or pin strength.
Best Regards,
Jaehoon Chung
On 08/06/2014 03:54 PM, Jean-Michel Hautbois wrote:
> 2014-08-06 3:15 GMT+02:00 Hsin-Hsiang Tseng <hsinhsiangtseng@gmail.com>:
>> from your log, maybe you should check the driver use byte mode or
>> sector mode to access eMMC.
>> Because the capacity of eMMC which you used is less or equal to 2GB.
>
> How can I know that ?
> FYI :
> $> cat /sys/kernel/debug/mmc1/ios
> clock: 52000000 Hz
> actual clock: 49500000 Hz
> vdd: 21 (3.3 ~ 3.4 V)
> bus mode: 2 (push-pull)
> chip select: 0 (don't care)
> power mode: 2 (on)
> bus width: 3 (8 bits)
> timing spec: 8 (mmc DDR52)
> signal voltage: 0 (3.30 V)
> --
> 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:[~2014-08-06 11:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 14:26 Sandisk MMC I/O errors Jean-Michel Hautbois
2014-08-05 15:13 ` Fabio Estevam
2014-08-05 15:20 ` Jean-Michel Hautbois
2014-08-05 15:35 ` Fabio Estevam
2014-08-05 15:44 ` Jean-Michel Hautbois
2014-08-05 15:54 ` Jean-Michel Hautbois
2014-08-05 15:59 ` Fabio Estevam
2014-08-05 16:01 ` Jean-Michel Hautbois
2014-08-06 1:15 ` Hsin-Hsiang Tseng
2014-08-06 6:54 ` Jean-Michel Hautbois
2014-08-06 11:44 ` Jaehoon Chung [this message]
2014-08-06 13:27 ` Jean-Michel Hautbois
2014-08-06 13:37 ` Fabio Estevam
2014-08-06 14:21 ` Jean-Michel Hautbois
2014-08-07 6:59 ` Jean-Michel Hautbois
2014-08-07 7:18 ` Jean-Michel Hautbois
2014-08-07 7:51 ` Jaehoon Chung
2014-08-07 7:54 ` Jean-Michel Hautbois
2014-08-07 8:54 ` Jean-Michel Hautbois
2014-08-07 15:02 ` Hsin-Hsiang Tseng
2014-08-07 15:44 ` Jean-Michel Hautbois
2014-08-08 3:12 ` Jaehoon Chung
2014-08-08 7:06 ` Jean-Michel Hautbois
2014-08-08 7:54 ` Jean-Michel Hautbois
2014-08-09 9:05 ` Hsin-Hsiang Tseng
2014-08-28 7:28 ` Jean-Michel Hautbois
2014-08-28 14:20 ` Hsin-Hsiang Tseng
2014-08-28 14:31 ` Jean-Michel Hautbois
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=53E21515.3060807@samsung.com \
--to=jh80.chung@samsung.com \
--cc=festevam@gmail.com \
--cc=hsinhsiangtseng@gmail.com \
--cc=jean-michel.hautbois@vodalys.com \
--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 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.