[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z_TZxXORT8H99qv4@shikoro>
Date: Tue, 8 Apr 2025 10:09:41 +0200
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: Ulf Hansson <ulf.hansson@...aro.org>
Cc: linux-mmc@...r.kernel.org, Adrian Hunter <adrian.hunter@...el.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>,
Avri Altman <Avri.Altman@...disk.com>,
linux-renesas-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/5] mmc: core: Further avoid re-storing power to the
eMMC before a shutdown
> @@ -2187,11 +2198,12 @@ static int mmc_shutdown(struct mmc_host *host)
> int err = 0;
>
> /*
> - * In a specific case for poweroff notify, we need to resume the card
> - * before we can shutdown it properly.
> + * If the card remains suspended at this point and it was done by using
> + * the sleep-cmd (CMD5), we may need to re-initialize it first, to allow
> + * us to send the preferred poweroff-notification cmd at shutdown.
> */
> if (mmc_can_poweroff_notify(host->card) &&
> - !(host->caps2 & MMC_CAP2_FULL_PWR_CYCLE))
> + !mmc_host_can_poweroff_notify(host, true))
Ooookay, I think I got this logic now. I think it makes sense to make it
more explicit in the comment, though:
"This is then the case when the card is able to handle poweroff
notifications in general but the host could not initiate those for
suspend."
Something like this?
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists