From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: "ulf.hansson@linaro.org" <ulf.hansson@linaro.org>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH/RFC] mmc: core: Issue power_off_notify for eMMC Suspend-to-RAM
Date: Thu, 4 Jun 2020 12:17:11 +0000 [thread overview]
Message-ID: <TY2PR01MB3692FD4D8058D5EEFC761D47D8890@TY2PR01MB3692.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <1589887988-7362-1-git-send-email-yoshihiro.shimoda.uh@renesas.com>
Hi again,
> From: Yoshihiro Shimoda, Sent: Tuesday, May 19, 2020 8:33 PM
>
> The commit 432356793415 ("mmc: core: Enable power_off_notify for
> eMMC shutdown sequence") enabled the power off notification
> even if MMC_CAP2_POWEROFF_NOTIFY (MMC_CAP2_FULL_PWR_CYCLE now) is
> not set. However, the mmc core lacks to issue the power off
> notificaiton when Suspend-to-{RAM,Disk} happens on the system.
>
> So, add Suspend-to-RAM support at first because this is easy to
> check by using pm_suspend_target_state condition on _mmc_suspend().
>
> Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
I'd like to add more detail why this patch is needed.
I think we should think some events (which are Shutdown, Suspend-to-idle,
Suspend-to-RAM) for the Power off Notification control.
I described these events like below.
Assumption of the host : MMC_CAP2_FULL_PWR_CYCLE=false
Assumption of the eMMC : in POWERED_ON
1) Event : Shutdown
- power : going to VCC=OFF & VCCQ=OFF
- ideal : Either POWER_OFF_LONG or POWER_OFF_SHORT
- current : POWER_OFF_LONG --> Perfect
- Remarks : the commit 432356793415
2) Event : Suspend-to-Idle
- power : Keep VCC=ON & VCCQ=ON
- ideal : issue MMC_SLEEP_AWAKE and keep the power (because the host could not change VCC=OFF)
- current : issue MMC_SLEEP_AWAKE and keep the power --> Perfect
- Remarks : IIUC, even if the eMMC is in POWERED_ON, a host can issue CMD5 (sleep).
3) Event : Suspend-to-RAM
- power : going to VCC=OFF & VCCQ=OFF
- ideal : Either POWER_OFF_LONG or POWER_OFF_SHORT (because the same as the "Shutdown" event)
- current : issue MMC_SLEEP_AWAKE --> NG
- Remarks : So, I tried to fix this by the patch.
In addition, we should also think about the event of unbind.
4) Event : Unbind
- power : Keep VCC=ON & VCCQ=ON
- ideal : NO_POWER_NOTIFICATION because user is possible to turn the power off
- current : Keep POWERED_ON --> NG
- Remarks : But, I didn't try to fix this yet.
Best regards,
Yoshihiro Shimoda
next prev parent reply other threads:[~2020-06-04 12:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 11:33 [PATCH/RFC] mmc: core: Issue power_off_notify for eMMC Suspend-to-RAM Yoshihiro Shimoda
2020-06-04 12:17 ` Yoshihiro Shimoda [this message]
2020-06-08 8:14 ` Ulf Hansson
2020-06-08 10:39 ` Yoshihiro Shimoda
2020-06-08 11:45 ` Ulf Hansson
2020-06-08 12:36 ` Geert Uytterhoeven
2020-06-08 14:50 ` Ulf Hansson
2020-06-09 10:29 ` Yoshihiro Shimoda
2020-06-08 7:57 ` Ulf Hansson
2020-06-08 10:38 ` Yoshihiro Shimoda
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=TY2PR01MB3692FD4D8058D5EEFC761D47D8890@TY2PR01MB3692.jpnprd01.prod.outlook.com \
--to=yoshihiro.shimoda.uh@renesas.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@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;
as well as URLs for NNTP newsgroup(s).