All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: linux-mmc@vger.kernel.org, ulf.hansson@linaro.org
Subject: Re: questions about runtime pm
Date: Mon, 18 Jan 2016 11:35:41 +0900	[thread overview]
Message-ID: <569C4F7D.40700@samsung.com> (raw)
In-Reply-To: <20160115150143.GA10117@odux.rfo.atmel.com>

Hi,

On 01/16/2016 12:01 AM, Ludovic Desroches wrote:
> On Tue, Dec 22, 2015 at 02:24:53PM +0100, Ludovic Desroches wrote:
>> Hi guys,
>>
>> I have recently added PM support for my driver but I don't have the
>> behavior I was expecting. I am wondering if I didn't do something wrong.
>>
>> I have implemented runtime_suspend in a very simple way, I call
>> sdhci_runtime_suspend_host() and I disable the clocks. It works pretty
>> well with the eMMC which is non removable but with a SD card... If I
>> have my SD card present on boot time, it is detected but
>> insertion/removal is not detected.
>>
>> Having a look to sdhci_runtime_suspend_host() internal, all the
>> interruptions are disabled expecting the card interrupt if it has been
>> set earlier.
>>
>> From my understanding, it means that if there is no activity on sdhci,
>> we will go to suspend and then we could wake up only on a software event
>> (or a sdio interrupt). How to manage card insertion/removal in this
>> case? My problem is so huge, I have probably missed something...

Is there any detection method for SD-card(removable card)?
Doesn't use Card-detect pin or Polling..?

Best Regards,
Jaehoon Chung

>>
>> Moreover, to avoid system PM, I have used pm_runtime_force_suspend but I
>> could not wake up on card insertion/removal too. Do I have to use system
>> PM if I want to manage this case?
>>
>> Thanks for your advices.
>>
>> Regards
>>
>> Ludovic
> 
> 
> Any feedback?
> 
> 
> Ludovic
> --
> 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
> 
> 


  reply	other threads:[~2016-01-18  2:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22 13:24 questions about runtime pm Ludovic Desroches
2016-01-15 15:01 ` Ludovic Desroches
2016-01-18  2:35   ` Jaehoon Chung [this message]
     [not found] <EMEW3|116e69362a474a99eb7966986654fb49p9RFXO07lm15g10|ecs.soton.ac.uk|526E83A9.8000703@ecs.soton.ac.uk>
2013-10-28 19:16 ` Questions about Runtime PM Alan Stern
2013-10-28 20:19   ` David C Niemi

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=569C4F7D.40700@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.