public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Manoj Iyer <manoj.iyer@canonical.com>
Cc: Chris Ball <cjb@laptop.org>, Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.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: Tue, 19 Jul 2011 07:27:58 +0800	[thread overview]
Message-ID: <20110719072758.20dd400e@jbarnes-e6510> (raw)
In-Reply-To: <alpine.DEB.2.02.1107131154000.3174@lazy>

On Wed, 13 Jul 2011 11:54:40 -0500 (CDT)
Manoj Iyer <manoj.iyer@canonical.com> wrote:

> 
> > On Wed, Jul 13 2011, Arnd Bergmann wrote:
> >> Not much. This card only has a 6MB/s write speed, which is well
> >> below what a 50 MHz bus can do. It mgiht be different on a fast
> >> eMMC device or a Sandisk Extreme Pro UHS-1 card.
> >
> > Okay, I see.  I think we're good for now, then -- hopefully anyone
> > using a UHS card on their laptop will see the printk when wondering
> > why their performance isn't great and get in touch with us, and we
> > can investigate more then.
> >
> > I've pushed Manoj's patch to mmc-next for 3.1 now, with the printk
> > changes and a stable@ tag.
> >
> 
> Thanks Chris!

Assuming you can't move the patch into the MMC driver itself, you can
add my acked-by for the PCI quirk addition.

Thanks,
Jesse

      reply	other threads:[~2011-07-18 23:28 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
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 [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=20110719072758.20dd400e@jbarnes-e6510 \
    --to=jbarnes@virtuousgeek.org \
    --cc=arnd@arndb.de \
    --cc=cjb@laptop.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