linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: Mirza Krak <mirza.krak@hostmobility.com>,
	Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: MMC card removal during suspend
Date: Thu, 01 Oct 2015 18:43:14 +0900	[thread overview]
Message-ID: <560D0032.4030505@samsung.com> (raw)
In-Reply-To: <CAJ=nTsuy2aD66DSc5kmEi79OjzPsXdOC2bx5-GxS=xy8LMCA=Q@mail.gmail.com>

On 10/01/2015 01:10 AM, Mirza Krak wrote:
> Hi again.
> 
> Thank you for your response Ulf.
> 
> I am going to start over though since I did not get everything right
> the first time.
> 
> As stated I am running the 4.1.5 Linux kernel and what I am actually
> using is a SD card. The host driver is sdhci-esdhc-imx.c.
> 
> And my initial issue was that on resume I get the following:
> [   31.848397] mmc0: card never left busy state
> [   31.848412] mmc0: error -110 during resume (card was removed?)
> [   31.848550] PM: resume of devices complete after 2062.936 msecs
> [   31.931086] PM: Finishing wakeup.
> [   31.931102] Restarting tasks ... done.
> [   31.954336] mmc0: card dade removed
> [   32.358711] mmc0: host does not support reading read-only switch,
> assuming write-enable
> [   32.391857] mmc0: new SD card at address aaaa
> [   32.418228] mmcblk0: mmc0:aaaa SU02G 1.84 GiB
> [   32.446402]  mmcblk0: p1
> [   32.835907] EXT4-fs (mmcblk0p1): recovery complete
> [   32.840873] EXT4-fs (mmcblk0p1): mounted filesystem with ordered
> data mode. Opts: (null)
> 
> And that was the reason of my initial questions on what is supposed to
> happen when suspending.

Almost MMC cards supposed that should be removed. So we are using "non-removable" property in dt-file.
By default, assume that card can be removed.
Since sd-card can be changed during suspend.
(we don't know whether card is changed or not if it doesn't register to wakeup source,)

> 
> The card IS actually "removed" when in suspended state since we cut
> the power-rail completely to the SD card.
> 
> I assume that this is a sdhci-esdhc-imx issue, but then I wonder what
> would be a proper fix for this.

Sorry, i don't fully understand what problem you want to fix. :)

Best Regards,
Jaehoon Chung

> 
> As stated before I get around this problem by adding a HACK to force
> removal of the SD card before suspending in mmc_pm_notify.
> 
> Sorry if I am spamming but I am trying to learn :).
> 
> Best Regards
> 
> Mirza Krak
> --
> 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
> 


      parent reply	other threads:[~2015-10-01  9:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30  6:46 MMC card removal during suspend Mirza Krak
2015-09-30 10:24 ` Ulf Hansson
2015-09-30 16:10   ` Mirza Krak
2015-10-01  9:39     ` Ulf Hansson
2015-10-01  9:43     ` Jaehoon Chung [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=560D0032.4030505@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=mirza.krak@hostmobility.com \
    --cc=ulf.hansson@linaro.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 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).