From: Ulf Hansson <ulf.hansson@linaro.org>
To: Azhar Shaikh <azhar.shaikh@intel.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] mmc: sdhci-pci: Set MMC_CAP_AGGRESSIVE_PM for BYT-related Intel controllers
Date: Thu, 30 Mar 2017 21:31:09 +0200 [thread overview]
Message-ID: <CAPDyKFpSw_CMUY85hJXzjWarMRzVMXw-Q76ndLc91Z49PzEiGA@mail.gmail.com> (raw)
In-Reply-To: <1490811393-109654-2-git-send-email-azhar.shaikh@intel.com>
On 29 March 2017 at 20:16, Azhar Shaikh <azhar.shaikh@intel.com> wrote:
> Set MMC_CAP_AGGRESSIVE_PM for BYT-related Intel SD card
> controllers.
>
> Signed-off-by: Azhar Shaikh <azhar.shaikh@intel.com>
Thanks, applied for next!
Kind regards
Uffe
> ---
> Changes in v2:
> - Rebased the patch on top of 'next' branch.
> - No code change.
>
> drivers/mmc/host/sdhci-pci-core.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/mmc/host/sdhci-pci-core.c b/drivers/mmc/host/sdhci-pci-core.c
> index 6c0440e..833072b 100644
> --- a/drivers/mmc/host/sdhci-pci-core.c
> +++ b/drivers/mmc/host/sdhci-pci-core.c
> @@ -630,16 +630,15 @@ static int byt_sdio_probe_slot(struct sdhci_pci_slot *slot)
> static int byt_sd_probe_slot(struct sdhci_pci_slot *slot)
> {
> byt_read_dsm(slot);
> - slot->host->mmc->caps |= MMC_CAP_WAIT_WHILE_BUSY;
> + slot->host->mmc->caps |= MMC_CAP_WAIT_WHILE_BUSY |
> + MMC_CAP_AGGRESSIVE_PM;
> slot->cd_idx = 0;
> slot->cd_override_level = true;
> if (slot->chip->pdev->device == PCI_DEVICE_ID_INTEL_BXT_SD ||
> slot->chip->pdev->device == PCI_DEVICE_ID_INTEL_BXTM_SD ||
> slot->chip->pdev->device == PCI_DEVICE_ID_INTEL_APL_SD ||
> - slot->chip->pdev->device == PCI_DEVICE_ID_INTEL_GLK_SD) {
> + slot->chip->pdev->device == PCI_DEVICE_ID_INTEL_GLK_SD)
> slot->host->mmc_host_ops.get_cd = bxt_get_cd;
> - slot->host->mmc->caps |= MMC_CAP_AGGRESSIVE_PM;
> - }
>
> return 0;
> }
> --
> 1.9.1
>
next prev parent reply other threads:[~2017-03-30 19:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 18:08 [PATCH 1/2] mmc: sdhci-acpi: Set MMC_CAP_AGGRESSIVE_PM for BYT-related Intel controllers Azhar Shaikh
2017-03-28 18:08 ` [PATCH 2/2] mmc: sdhci-pci: " Azhar Shaikh
2017-03-29 18:16 ` [PATCH v2 1/2] mmc: sdhci-acpi: " Azhar Shaikh
2017-03-29 18:16 ` [PATCH v2 2/2] mmc: sdhci-pci: " Azhar Shaikh
2017-03-30 7:41 ` Adrian Hunter
2017-03-30 19:31 ` Ulf Hansson [this message]
2017-03-30 7:41 ` [PATCH v2 1/2] mmc: sdhci-acpi: " Adrian Hunter
2017-03-30 19:31 ` Ulf Hansson
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=CAPDyKFpSw_CMUY85hJXzjWarMRzVMXw-Q76ndLc91Z49PzEiGA@mail.gmail.com \
--to=ulf.hansson@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=azhar.shaikh@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.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;
as well as URLs for NNTP newsgroup(s).