From: Jaehoon Chung <jh80.chung@samsung.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Alex Lemberg <Alex.Lemberg@sandisk.com>
Cc: Avi Shchislowski <Avi.Shchislowski@sandisk.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
Chris Ball <chris@printf.net>
Subject: Re: [PATCH] mmc: sleep notification
Date: Fri, 13 Mar 2015 20:46:15 +0900 [thread overview]
Message-ID: <5502CE07.2060002@samsung.com> (raw)
In-Reply-To: <CAPDyKFqLUBYUx9XrhnMeUtf8HU_=4PH_4Vf7m8mM-CT63jG24Q@mail.gmail.com>
On 03/12/2015 06:09 PM, Ulf Hansson wrote:
> [...]
>
>>>> Also, I think we need to clarify one more point for this patch:
>>>> As was mentioned in commit message - Sleep_Notification can be interrupted
>>> by HPI.
>>>> This allows not blocking the host during the Sleep_Notification busy
>>>> time and allows accepting requests coming during this stage. Thus,
>>>> without having HPI supported, suspend/resume process might be
>>>> influenced by Sleep_Notification busy time, and this should not happen -
>>> suspend/resume should be done in very fast and not blocking manner.
>>>
>>> I fail to understand your comment here.
>>>
>>> Please tell me at what point(s) your think it make sense to issue the
>>> SLEEP_NOTIFICATION? If that is during the suspend phase, then a HPI request
>>> can't be triggered.
>>
>> I think SLEEP_NOTIFICATION should be issued on mmc_pm_notify() call,
>> on PM_SUSPEND_PREPARE case.
>
> So, exactly why is that to prefer, comparing doing it in system PM
> ->suspend() callback?
Actually, i didn't know the benefit of this feature.
Best Regards,
Jaehoon Chung
>
> Kind regards
> Uffe
> --
> 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
>
next prev parent reply other threads:[~2015-03-13 11:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 9:36 [PATCH] mmc: sleep notification Avi Shchislowski
2015-03-10 12:07 ` Ulf Hansson
2015-03-10 14:32 ` Alex Lemberg
2015-03-11 11:50 ` Ulf Hansson
2015-03-11 18:38 ` Alex Lemberg
2015-03-12 9:09 ` Ulf Hansson
2015-03-13 11:46 ` Jaehoon Chung [this message]
2015-03-16 11:37 ` Alex Lemberg
2015-03-16 13:34 ` Ulf Hansson
2015-03-16 16:58 ` Alex Lemberg
2015-03-17 10:43 ` Ulf Hansson
2015-03-27 12:13 ` Alex Lemberg
2015-03-27 12:57 ` Ulf Hansson
2015-03-31 16:22 ` Alex Lemberg
2015-04-01 11:46 ` Ulf Hansson
2015-04-06 13:44 ` Alex Lemberg
2015-04-08 9:49 ` Ulf Hansson
2015-03-10 13:36 ` Adrian Hunter
2015-03-10 16:32 ` Alex Lemberg
2015-03-10 17:22 ` Ulf Hansson
2015-03-10 18:01 ` Alex Lemberg
2015-03-15 9:04 ` Avi Shchislowski
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=5502CE07.2060002@samsung.com \
--to=jh80.chung@samsung.com \
--cc=Alex.Lemberg@sandisk.com \
--cc=Avi.Shchislowski@sandisk.com \
--cc=chris@printf.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox