From: Yann Gautier <yann.gautier@foss.st.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Russell King <linux@armlinux.org.uk>,
Rob Herring <robh+dt@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
<linux-arm-msm@vger.kernel.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
<devicetree@vger.kernel.org>
Subject: Question about MMC_PM_KEEP_POWER in MMCI driver
Date: Wed, 25 Aug 2021 16:34:10 +0200 [thread overview]
Message-ID: <ccb2dad1-c8c1-9f19-92c4-7faf2b787e6d@foss.st.com> (raw)
Hi,
In drivers/mmc/host/mmci.c, MMC_PM_KEEP_POWER is unconditionally enabled.
This prevents correct low-power sequence on STM32MP157C-DK2 board which
embeds a Wifi chip brcm,bcm4329-fmac (this wifi part has not yet been
sent upstream).
This MMC_PM_KEEP_POWER can be taken from DT with the property
keep-power-in-suspend. This is what is done for other MMC drivers.
I wonder what should be the best solution for this.
1) Remove MMC_PM_KEEP_POWER from the driver, and modify all SoC device
tree files embedding a arm,pl18x with adding keep-power-in-suspend;
property (except stm32mp151.dtsi file).
This can be easy to do (~10 files to modify). But that could be more
board dependent, if an SDIO chip is plugged on this MMC IP.
And the name keep-power-in-suspend can be misleading as it only applies
to SDIO.
2) Remove MMC_PM_KEEP_POWER from the driver, and modify board DT files
with the property. This could be a difficult task to find all those
boards. And this should be applied only for SDIO configs.
3) Just modify the driver to apply this capability for all MMCI chips
but STM32. This could be done in the dedicated file, in
sdmmc_variant_init() function. But some boards based on STM32MP15 chip
might want to keep this capability.
All advice is welcome.
Thanks,
Yann
next reply other threads:[~2021-08-25 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 14:34 Yann Gautier [this message]
2021-08-30 13:43 ` Question about MMC_PM_KEEP_POWER in MMCI driver Ulf Hansson
2021-09-01 7:32 ` 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=ccb2dad1-c8c1-9f19-92c4-7faf2b787e6d@foss.st.com \
--to=yann.gautier@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=robh+dt@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).