From: Philipp Zabel <p.zabel@pengutronix.de>
To: Yann Gautier <yann.gautier@foss.st.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
Christophe Kerello <christophe.kerello@foss.st.com>,
Linus Walleij <linus.walleij@linaro.org>,
Ludovic Barre <ludovic.barre@foss.st.com>,
Russell King <linux@armlinux.org.uk>, Marek Vasut <marex@denx.de>,
kernel@dh-electronics.com,
Manivannan Sadhasivam <mani@kernel.org>,
Grzegorz Szymaszek <gszymaszek@short.pl>
Subject: Re: [PATCH v2] mmc: mmci: manage MMC_PM_KEEP_POWER per variant config
Date: Mon, 14 Mar 2022 14:05:54 +0100 [thread overview]
Message-ID: <1e620fa18fa34ca1f65558e3a52f79f81ff20634.camel@pengutronix.de> (raw)
In-Reply-To: <20220314125554.190574-1-yann.gautier@foss.st.com>
Hi Yann,
On Mo, 2022-03-14 at 13:55 +0100, Yann Gautier wrote:
> Add a disable_keep_power field in variant_data struct. The
> MMC_PM_KEEP_POWER flag will be enabled if disable_keep_power is not
> set.
> It is only set to true for stm32_sdmmc variants.
>
> The issue was seen on STM32MP157C-DK2 board, which embeds a wifi
> chip.
> It doesn't correctly support low power on this board. The Wifi chip
> awaits an always-on regulator, but it was connected to v3v3 which is
> off
> in low-power sequence. MMC_PM_KEEP_POWER should then be disabled.
>
> The flag can still be enabled through DT property:
> keep-power-in-suspend.
>
> Signed-off-by: Yann Gautier <yann.gautier@foss.st.com>
> ---
> Update in v2:
> Reword commit message to better explain the issue.
>
> Resend the patch alone. It was previoulsy in a series [1] for which
> the
> other patches will be reworked.
>
> [1]
> https://lore.kernel.org/lkml/20220304135134.47827-1-yann.gautier@foss.st.com/
>
> drivers/mmc/host/mmci.c | 5 ++++-
> drivers/mmc/host/mmci.h | 1 +
> 2 files changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/host/mmci.c b/drivers/mmc/host/mmci.c
> index 45b8608c935c..0e2f2f5d6a52 100644
> --- a/drivers/mmc/host/mmci.c
> +++ b/drivers/mmc/host/mmci.c
> @@ -274,6 +274,7 @@ static struct variant_data variant_stm32_sdmmc =
> {
> .busy_detect = true,
> .busy_detect_flag = MCI_STM32_BUSYD0,
> .busy_detect_mask = MCI_STM32_BUSYD0ENDMASK,
> + .disable_keep_power = true,
> .init = sdmmc_variant_init,
> };
>
> @@ -301,6 +302,7 @@ static struct variant_data variant_stm32_sdmmcv2
> = {
> .busy_detect = true,
> .busy_detect_flag = MCI_STM32_BUSYD0,
> .busy_detect_mask = MCI_STM32_BUSYD0ENDMASK,
> + .disable_keep_power = true,
> .init = sdmmc_variant_init,
> };
>
> @@ -2172,7 +2174,8 @@ static int mmci_probe(struct amba_device *dev,
> host->stop_abort.flags = MMC_RSP_R1B | MMC_CMD_AC;
>
> /* We support these PM capabilities. */
> - mmc->pm_caps |= MMC_PM_KEEP_POWER;
> + if (!variant->disable_keep_power)
> + mmc->pm_caps |= MMC_PM_KEEP_POWER;
>
> /*
> * We can do SGIO
> diff --git a/drivers/mmc/host/mmci.h b/drivers/mmc/host/mmci.h
> index e1a9b96a3396..2cad1ef9766a 100644
> --- a/drivers/mmc/host/mmci.h
> +++ b/drivers/mmc/host/mmci.h
> @@ -361,6 +361,7 @@ struct variant_data {
> u32 opendrain;
> u8 dma_lli:1;
> u32 stm32_idmabsize_mask;
> + u8 disable_keep_power:1;
There are already four separate bitfields in struct variant_data, why
not move this up into one of them?
regards
Philipp
next prev parent reply other threads:[~2022-03-14 13:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 9:52 [PATCH RESEND] " Yann Gautier
2022-03-14 11:17 ` Ulf Hansson
2022-03-14 12:20 ` Yann Gautier
2022-03-14 12:53 ` Ulf Hansson
2022-03-14 12:55 ` [PATCH v2] " Yann Gautier
2022-03-14 13:03 ` Ulf Hansson
2022-03-14 14:34 ` Yann Gautier
2022-03-14 16:18 ` Ulf Hansson
2022-03-14 16:51 ` Yann Gautier
2022-03-15 9:07 ` Ulf Hansson
2022-03-15 10:07 ` Yann Gautier
2022-03-15 12:30 ` Ulf Hansson
2022-03-14 13:05 ` Philipp Zabel [this message]
2022-03-14 13:45 ` Yann Gautier
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=1e620fa18fa34ca1f65558e3a52f79f81ff20634.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=christophe.kerello@foss.st.com \
--cc=gszymaszek@short.pl \
--cc=kernel@dh-electronics.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=ludovic.barre@foss.st.com \
--cc=mani@kernel.org \
--cc=marex@denx.de \
--cc=ulf.hansson@linaro.org \
--cc=yann.gautier@foss.st.com \
/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
all inboxes | Powered by JetHome®