public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: linux-mmc <linux-mmc@vger.kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-pm <linux-pm@lists.linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Philip Langdale <philipl@overt.org>
Subject: Re: [PATCH] Two fixes for my mmc/sd cardreader
Date: Mon, 21 Jun 2010 22:21:44 +0300	[thread overview]
Message-ID: <1277148104.4241.1.camel@maxim-laptop> (raw)
In-Reply-To: <1276809695.28201.13.camel@maxim-laptop>

On Fri, 2010-06-18 at 00:21 +0300, Maxim Levitsky wrote: 
> Hi,
> 
> These are 2 fixes for my card reader.
> 
> 
> First patch fixes old issue with system hand on suspend to disk/ram with
> mmc card inserted.
> I updated description, and pm notification registration order.
> I think this patch can an should go to 2.6.35, because it fixes long
> standing and nasty regression.
> 
> The second patch is a result of my work trying to understand why my card
> reader sometimes dies on resume.
> This reader has a special MMC function which steals MMC cards, and until
> now had no driver. A way to disable it was found, and while it works, it
> has (at least here) a side effect of killing the controller on resume
> from ram/disk (and it happens often, and doesn't depend of whether card
> was in slot or not during suspend).
> 
> Fortunately it turned out that MMC part is _almost_ standard SDHCI
> controller.
> This patch adds support for this device to standard sdhci driver.
> Unfortunately, this support still contais small hack.
> It waits 1/2 of a second on resume before initializing the controller.
> Not doing so, and resuming with MMC card present results in confused
> controller. It is not dead though. A card reinsert makes it work again
> with all cards.
> Yet the 1st patch is must for this because otherwise mmc core seeing
> that controller doesn't respond, removes the card, therefore hangs the
> system.
> It doesn't happen when I wait these 1/2 of second though.
> 
> I think that this patch is also ok for 2.6.35, because it only adds new
> functionality.
> You are free to disable MMC controller using the same
> CONFIG_MMC_RICOH_MMC.
> 
> If you don't disable it though, instead of full lack of functionality
> you will get full featured MMC controller.
> 
> Best regards,
> Maxim Levitsky
> 
> 
> 
ping


  parent reply	other threads:[~2010-06-21 19:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17 21:21 [PATCH] Two fixes for my mmc/sd cardreader Maxim Levitsky
2010-06-17 21:23 ` [PATCH 1/2] MMC: fix all hangs related to mmc/sd card insert/removal during suspend/resume Maxim Levitsky
2010-06-21 20:04   ` Adrian Hunter
2010-06-21 20:14     ` Maxim Levitsky
2010-06-21 20:26       ` Rafael J. Wysocki
2010-06-22  0:03         ` Maxim Levitsky
2010-06-22  9:19           ` Rafael J. Wysocki
2010-06-22 21:17             ` Maxim Levitsky
2010-06-22 21:53               ` Rafael J. Wysocki
2010-06-22 22:20                 ` Andrew Morton
2010-06-23  0:16                   ` Rafael J. Wysocki
2010-06-23  3:08                   ` MMC tree (Was: Re: [PATCH 1/2] MMC: fix all hangs related to mmc/sd card insert/removal during suspend/resume.) Stephen Rothwell
2010-06-23  3:52                     ` Andrew Morton
2010-08-13  9:24   ` [PATCH] mmc: build fix: mmc_pm_notify is only available with CONFIG_PM=y Uwe Kleine-König
2010-08-13 10:01     ` Maxim Levitsky
2010-08-16  7:51       ` Maxim Levitsky
2010-08-16  5:28     ` Kukjin Kim
2010-06-17 21:23 ` [PATCH 2/2] mmc: make sdhci work with ricoh mmc controller Maxim Levitsky
2010-06-21 19:21 ` Maxim Levitsky [this message]
2010-06-21 19:39   ` [PATCH] Two fixes for my mmc/sd cardreader Andrew Morton
2010-06-21 19:50     ` Maxim Levitsky

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=1277148104.4241.1.camel@maxim-laptop \
    --to=maximlevitsky@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=philipl@overt.org \
    --cc=rjw@sisk.pl \
    /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