linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: linux-mmc@vger.kernel.org
Cc: John Stultz <john.stultz@linaro.org>, Chris Ball <cjb@laptop.org>,
	Arnd Bergmann <arnd@arndb.de>, Dima Zavin <dima@android.com>,
	Bentao Zou <bzou1@motorola.com>,
	David Ding <david.j.ding@motorola.com>,
	San Mehat <san@google.com>, Colin Cross <ccross@android.com>,
	Todd Poynor <toddpoynor@google.com>
Subject: [PATCH 0/6] Trivial MMC patches from Android
Date: Fri, 22 Apr 2011 18:01:36 -0700	[thread overview]
Message-ID: <1303520502-32171-1-git-send-email-john.stultz@linaro.org> (raw)

I've recently spent some time looking through the Android tree,
and while there are some controversial interface changes, there
are also a number of patches which look to be simply fixes that
have not yet made it upstream. 

In order to make sure these fixes don't get overlooked, I'm trying
to filter out these small changes into narrowly scoped topic branches
then sending them out for review and comment.

Now, I'm not proposing that these changes be merged as-is. It
may very well be that, unknown to me, android developers have
already tried to submit these patches and they have been rejected
for good reason. Or some patches may very well be necessary hacks
to get thing shipping while deeper fixes are being worked on. If
that is the case, let me know and forgive me for the noise.

Authors: In many cases, the patches are lacking good commit
messages, so I cannot advocate for them very well. Your assistance
in answering questions that come up would be appreciated.

Maintainers: If you do find any of these patches distasteful,
that's fine, I'll be happy to drop them from my tree for now.
I really don't want to stir up another huge mail thread over these 
small patches, but I'd appreciate if you'd consider them as a
bug report illustrating an issue or a desired feature, and suggest 
what you see as a reasonable way to accomplish the desired
functionality presented in the patch.

The following patches are general MMC changes:

The first three look like fairly straightforward fixes.

The second three introduce a paranoid init option which retries
a few times on failure. The #ifdefs clearly need to be cleaned
up, but I wanted to send it out for comment on the basic
functionality.

You can also find the other trivial tree branches I'm working
on here (fair warning, I re-base this tree frequently): 
http://git.linaro.org/gitweb?p=people/jstultz/android-trivial.git;a=summary

thanks
-john

CC: Chris Ball <cjb@laptop.org>
CC: Arnd Bergmann <arnd@arndb.de>
CC: Dima Zavin <dima@android.com>
CC: Bentao Zou <bzou1@motorola.com>
CC: David Ding <david.j.ding@motorola.com>
CC: San Mehat <san@google.com>
CC: Colin Cross <ccross@android.com>
CC: Todd Poynor <toddpoynor@google.com>


Colin Cross (1):
  mmc_block: Allow more than 8 partitions per card

David Ding (1):
  mmc: block: Resume multi-block reads after transient read errors.

San Mehat (3):
  mmc: sd: Add new CONFIG_MMC_PARANOID_SD_INIT for enabling retries
    during SD detection
  mmc: sd: When resuming, try a little harder to init the card
  mmc: sd: Add retries in re-detection

Todd Poynor (1):
  sdhci: Always pass clock request value zero to set_clock host op

 drivers/mmc/card/block.c |    9 ++---
 drivers/mmc/core/Kconfig |    9 +++++
 drivers/mmc/core/sd.c    |   84 ++++++++++++++++++++++++++++++++++++++++++++-
 drivers/mmc/host/sdhci.c |    2 +-
 4 files changed, 96 insertions(+), 8 deletions(-)

-- 
1.7.3.2.146.gca209


             reply	other threads:[~2011-04-23  1:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-23  1:01 John Stultz [this message]
2011-04-23  1:01 ` [PATCH 1/6] mmc: block: Resume multi-block reads after transient read errors John Stultz
2011-04-26 13:19   ` Arnd Bergmann
2011-04-27  8:16     ` Adrian Hunter
2011-04-27  8:42       ` Andrei Warkentin
2011-04-23  1:01 ` [PATCH 2/6] mmc_block: Allow more than 8 partitions per card John Stultz
2011-04-26 13:22   ` Arnd Bergmann
2011-04-26 16:10     ` Colin Cross
2011-04-26 16:13       ` Arnd Bergmann
2011-04-23  1:01 ` [PATCH 3/6] sdhci: Always pass clock request value zero to set_clock host op John Stultz
2011-04-23  1:01 ` [PATCH 4/6] mmc: sd: Add new CONFIG_MMC_PARANOID_SD_INIT for enabling retries during SD detection John Stultz
2011-04-26 13:35   ` Arnd Bergmann
2011-04-23  1:01 ` [PATCH 5/6] mmc: sd: When resuming, try a little harder to init the card John Stultz
2011-04-26 13:39   ` Arnd Bergmann
2011-04-23  1:01 ` [PATCH 6/6] mmc: sd: Add retries in re-detection John Stultz
2011-04-26 13:42   ` Arnd Bergmann

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=1303520502-32171-1-git-send-email-john.stultz@linaro.org \
    --to=john.stultz@linaro.org \
    --cc=arnd@arndb.de \
    --cc=bzou1@motorola.com \
    --cc=ccross@android.com \
    --cc=cjb@laptop.org \
    --cc=david.j.ding@motorola.com \
    --cc=dima@android.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=san@google.com \
    --cc=toddpoynor@google.com \
    /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;
as well as URLs for NNTP newsgroup(s).