From: Marek Vasut <marex@nabladev.com>
To: Ulf Hansson <ulf.hansson@oss.qualcomm.com>
Cc: linux-mmc@vger.kernel.org,
Christophe Kerello <christophe.kerello@foss.st.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Ulf Hansson <ulfh@kernel.org>,
kernel@dh-electronics.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH] mmc: mmci: stm32: handle mmc power up
Date: Thu, 12 Nov 2026 02:22:10 +0100 [thread overview]
Message-ID: <c3cbd7ab-e689-4a9b-b311-af43980738d2@nabladev.com> (raw)
In-Reply-To: <CAPx+jO89Z0Z241L1jyB_3sUygdEwGicqT-WfHc6ppG8egHUO2w@mail.gmail.com>
On 11/11/26 12:45 PM, Ulf Hansson wrote:
Hello Ulf,
>>>> - if (ios.power_mode == MMC_POWER_OFF) {
>>>> + if (ios.power_mode == MMC_POWER_OFF ||
>>>> + ios.power_mode == MMC_POWER_UP) {
>>>> /* Only a reset could power-off sdmmc */
>>>> reset_control_assert(host->rst);
>>>> udelay(2);
>>>
>>> What exactly will this reset?
>> The controller.
>
> Okay, I see.
>
> In that case, this reset also makes us reset preceding updates to any
> other registers, for example the clock register. I would not recommend
> doing that here, but perhaps there is no better option.
Does that pose a problem in the MMC_POWER_OFF/UP state ? I agree this
would pose a problem in the MMC_POWER_ON state, but here the card is not ON.
> If I may I suggest an alternative solution, perhaps we can manage this
> in the ->runtime_resume() callback instead. If the power_mode ==
> MMC_POWER_OFF, perhaps do this reset there instead? Would that work?
>
> Anothing thing that caught my eyes was the MCI_STM32_PWR_CYC bit that
> gets written at MMC_POWER_OFF. This bit becomes cached in
> host->pwr_reg, hence it's also rewritten at MMC_POWER_ON. Is that
> intentional?
I _think_ so, this seems to be used to power cycle the card.
prev parent reply other threads:[~2026-11-12 6:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 21:53 Marek Vasut
2026-11-10 13:32 ` Ulf Hansson
2026-11-11 2:27 ` Marek Vasut
2026-11-11 11:45 ` Ulf Hansson
2026-11-12 1:22 ` Marek Vasut [this message]
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=c3cbd7ab-e689-4a9b-b311-af43980738d2@nabladev.com \
--to=marex@nabladev.com \
--cc=alexandre.torgue@foss.st.com \
--cc=christophe.kerello@foss.st.com \
--cc=kernel@dh-electronics.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=ulf.hansson@oss.qualcomm.com \
--cc=ulfh@kernel.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
all inboxes | Powered by JetHome®