From: Adrian Hunter <adrian.hunter@intel.com>
To: Avi Shchislowski <avi.shchislowski@sandisk.com>, ulf.hansson@linaro.org
Cc: linux-mmc@vger.kernel.org, chris@printf.net, Alex.Lemberg@sandisk.com
Subject: Re: [PATCH] mmc: sleep notification
Date: Tue, 10 Mar 2015 15:36:14 +0200 [thread overview]
Message-ID: <54FEF34E.20205@intel.com> (raw)
In-Reply-To: <1425980197-823-1-git-send-email-avi.shchislowski@sandisk.com>
On 10/03/15 11:36, Avi Shchislowski wrote:
> This patch is implements the new additional state of
> Power_Off_Notification – SLEEP_NOTIFICATION.
> Until now, the implementation of Power_Off_Notification
> supported only three modes – POWERED_ON (0x01),
> POWER_OFF_SHORT (0x02) and POWER_OFF_LONG (0x03).
>
> As part of eMMC5.0 before moving to Sleep state hosts may set the
> POWER_OFF_NOTIFICATION byte to SLEEP_NOTIFICATION (0x04).
> After setting SLEEP_NOTIFICATION, host should wait for
> the busy line to be de-asserted.
> The max timeout allowed for busy line de-assertion defined
> in SLEEP_NOTIFICATION_TIME byte in EXT_CSD [216].
> HPI may interrupt the SLEEP_NOTIFICATION operation.
> In that case POWER_OFF_NOTIFICATION byte will restore to POWERED_ON.
Is it so that the point of SLEEP_NOTIFICATION is to notify that
VCC will be powered off after the device is put to sleep by CMD5?
At the moment, the card does not get put to sleep if there is
support for power-off-notification?
next prev parent reply other threads:[~2015-03-10 13:38 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
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 [this message]
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=54FEF34E.20205@intel.com \
--to=adrian.hunter@intel.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