From: Adrian Hunter <adrian.hunter@intel.com>
To: Erick Shepherd <erick.shepherd@ni.com>
Cc: <brad.mouring@ni.com>, <gratian.crisan@emerson.com>,
<kyle.roeschley@ni.com>, <linux-kernel@vger.kernel.org>,
<linux-mmc@vger.kernel.org>, <ulf.hansson@linaro.org>
Subject: Re: [PATCH] mmc: core: Wait for Vdd to settle on card power off
Date: Thu, 13 Mar 2025 10:20:52 +0200 [thread overview]
Message-ID: <802daedb-d82c-4d0b-8e69-d166c169cbb1@intel.com> (raw)
In-Reply-To: <20250313033552.1505631-1-erick.shepherd@ni.com>
On 13/03/25 05:35, Erick Shepherd wrote:
>> What about something like this?
>
>> diff --git a/drivers/mmc/host/sdhci-pci-core.c b/drivers/mmc/host/sdhci-pci-core.c
>> index 1f0bd723f011..0789df732e93 100644
>> --- a/drivers/mmc/host/sdhci-pci-core.c
>> +++ b/drivers/mmc/host/sdhci-pci-core.c
>> @@ -610,8 +610,11 @@ static void sdhci_intel_set_power(struct sdhci_host *host, unsigned char mode,
>
>> sdhci_set_power(host, mode, vdd);
>
>> - if (mode == MMC_POWER_OFF)
>> + if (mode == MMC_POWER_OFF) {
>> + if (slot->chip->pdev->device == PCI_DEVICE_ID_INTEL_APL_SD)
>> + usleep_range(15000, 17500);
>> return;
>> + }
>
>> /*
>> * Bus power might not enable after D3 -> D0 transition due to the
>
> I talked to one of our digital hardware engineers who worked on this
> issue. He believes that the issue is likely affecting more than just
> Apollo Lake devices and recommended keeping the delay for all of our
> devices. Could something like this work?
>
> --- a/drivers/mmc/host/sdhci.c
> +++ b/drivers/mmc/host/sdhci.c
> @@ -2176,6 +2176,9 @@ EXPORT_SYMBOL_GPL(sdhci_set_power_noreg);
> void sdhci_set_power(struct sdhci_host *host, unsigned char mode,
> unsigned short vdd)
> {
> + if (mode == MMC_POWER_OFF)
> + usleep_range(15000, 17500);
> +
> if (IS_ERR(host->mmc->supply.vmmc))
> sdhci_set_power_noreg(host, mode, vdd);
> else
sdhci is used by a number of drivers (drivers/mmc/host/sdhci*)
that typically use the regulator framework to meet voltage
requirements. So that is not the right place to make changes.
It would be best to put the affected PCI device IDs into
sdhci_intel_set_power() as I showed.
next prev parent reply other threads:[~2025-03-13 8:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 21:46 [PATCH] mmc: core: Wait for Vdd to settle on card power off Erick Shepherd
2025-02-13 10:22 ` Avri Altman
2025-03-05 18:38 ` Adrian Hunter
2025-03-07 17:46 ` Erick Shepherd
2025-03-07 18:53 ` Adrian Hunter
2025-03-07 21:16 ` Erick Shepherd
2025-03-12 12:44 ` Adrian Hunter
2025-03-13 3:35 ` Erick Shepherd
2025-03-13 8:20 ` Adrian Hunter [this message]
2025-03-13 20:44 ` Erick Shepherd
2025-03-14 5:56 ` Adrian Hunter
-- strict thread matches above, loose matches on Subject: below --
2017-09-21 17:47 Kyle Roeschley
2017-09-22 9:38 ` Ulf Hansson
2017-09-22 13:57 ` Kyle Roeschley
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=802daedb-d82c-4d0b-8e69-d166c169cbb1@intel.com \
--to=adrian.hunter@intel.com \
--cc=brad.mouring@ni.com \
--cc=erick.shepherd@ni.com \
--cc=gratian.crisan@emerson.com \
--cc=kyle.roeschley@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@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