From: Chris Ball <cjb@laptop.org>
To: Manoj Iyer <manoj.iyer@canonical.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, jbarnes@virtuousgeek.org,
matsumur@nts.ricoh.co.jp, linux-pci@vger.kernel.org,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: Added quirks for Ricoh 1180:e823 lower base clock frequency
Date: Mon, 18 Jul 2011 17:05:32 -0400 [thread overview]
Message-ID: <m2d3h7b8pv.fsf@bob.laptop.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1107181546100.1677@lazy> (Manoj Iyer's message of "Mon, 18 Jul 2011 15:47:33 -0500 (CDT)")
Hi Manoj,
On Mon, Jul 18 2011, Manoj Iyer wrote:
> Right, without the patch I get..
>
> [ 52.526665] mmc0: new SDHC card at address e624
> [ 52.571228] mmcblk0: mmc0:e624 SD16G 14.8 GiB
> [ 52.591071] mmcblk0: retrying using single block read
> [ 52.593105] mmcblk0: error -84 transferring data, sector 0, nr 8,
> card status 0x900
> [ 52.593109] end_request: I/O error, dev mmcblk0, sector 0
> [ 52.594594] mmcblk0: error -84 transferring data, sector 1, nr 7,
> card status 0x900
> [ 52.594604] end_request: I/O error, dev mmcblk0, sector 1
> [ 52.602893] quiet_error: 24 callbacks suppressed
> [ 52.602902] Buffer I/O error on device mmcblk0, logical block 0
> [ 52.605349] ldm_validate_partition_table(): Disk read failed.
> [ 52.605384] Dev mmcblk0: unable to read RDB block 0
> [ 52.607729] mmcblk0: unable to read partition table
> u@u:~$
>
> So, I cannot generate any comparison data with this SD card.
I see, thanks. So we're lacking any data on what speed the card would
normally provide. Perhaps you could try that card on a different
controller, just so we're able to see whether it's usually possible
to get closer to 45M/sec with it?
I think I'll take your patch as-is for 3.1 -- since if there is a
performance degradation, it's on cards that simply don't work at all
right now -- and if you're able to work on a followup patch that only
performs the clock-lowering after the first error, I think that'd be a
handy patch to have around. Does that sound good?
Thanks!
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-07-18 21:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 21:28 [Patch 0/1] mmc: Added quirks for Ricoh 1180:e823 lower base clock frequency Manoj Iyer
2011-07-11 21:28 ` [PATCH] " Manoj Iyer
2011-07-11 21:53 ` Chris Ball
2011-07-11 22:55 ` Manoj Iyer
2011-07-12 16:01 ` Manoj Iyer
2011-07-12 16:20 ` Chris Ball
2011-07-12 17:09 ` Manoj Iyer
2011-07-12 17:30 ` Chris Ball
2011-07-12 18:00 ` Arnd Bergmann
2011-07-13 14:45 ` Chris Ball
2011-07-13 15:42 ` Manoj Iyer
2011-07-13 16:35 ` Arnd Bergmann
2011-07-13 16:46 ` Manoj Iyer
2011-07-13 16:55 ` Chris Ball
2011-07-13 17:02 ` Manoj Iyer
2011-07-13 17:08 ` Chris Ball
2011-07-18 20:36 ` Manoj Iyer
2011-07-18 20:40 ` Chris Ball
2011-07-18 20:47 ` Manoj Iyer
2011-07-18 21:05 ` Chris Ball [this message]
2011-07-18 21:12 ` Manoj Iyer
2011-07-19 19:43 ` Manoj Iyer
2012-11-22 0:29 ` Chris Ball
2012-11-26 16:42 ` Manoj Iyer
2012-11-26 16:57 ` Chris Ball
2011-07-13 16:50 ` Chris Ball
2011-07-13 16:54 ` Manoj Iyer
2011-07-18 23:27 ` Jesse Barnes
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=m2d3h7b8pv.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=arnd@arndb.de \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=manoj.iyer@canonical.com \
--cc=matsumur@nts.ricoh.co.jp \
/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