From: Adrian Hunter <adrian.hunter@intel.com>
To: Patrick Thompson <ptf@google.com>,
Linux MMC development <linux-mmc@vger.kernel.org>
Cc: Sangwhan Moon <sxm@google.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc: sdhci-pci-core: Disable cqe for ASUS 1100FK family devices
Date: Tue, 13 Sep 2022 09:34:24 +0300 [thread overview]
Message-ID: <925b6e37-051f-927c-350a-cd767d88d72b@intel.com> (raw)
In-Reply-To: <20220912212847.1337868-1-ptf@google.com>
On 13/09/22 00:28, Patrick Thompson wrote:
> From: ptf <ptf@google.com>
>
> The CQE implementation for the eMMC in the ASUS 1100FK family of devices
> is broken. This causes installations to fail and thus we are disabling
> CQE for this family of devices.
>
> Signed-off-by: Patrick Thompson <ptf@google.com>
Acked-by: Adrian Hunter <adrian.hunter@intel.com>
> ---
>
> Hello,
>
> I was hoping to get some advice on adapting this patch to target the
> eMMC directly instead of a family of laptops. One idea is to use the
> PCI-id of the controller (in this case [8086:4dc4]). Would that make
> sense? Is there someone with more knowledge on the subject that could
> confirm that the [8086:4dc4] device doesn't have a working CQE?
In these cases the issue is suspected to be BIOS. Best solution is to
disable CQE.
>
> Thank you,
> Patrick
>
>
> drivers/mmc/host/sdhci-pci-core.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/host/sdhci-pci-core.c b/drivers/mmc/host/sdhci-pci-core.c
> index 622b7de96c7f..3ba0250559e7 100644
> --- a/drivers/mmc/host/sdhci-pci-core.c
> +++ b/drivers/mmc/host/sdhci-pci-core.c
> @@ -890,7 +890,8 @@ static bool glk_broken_cqhci(struct sdhci_pci_slot *slot)
> {
> return slot->chip->pdev->device == PCI_DEVICE_ID_INTEL_GLK_EMMC &&
> (dmi_match(DMI_BIOS_VENDOR, "LENOVO") ||
> - dmi_match(DMI_SYS_VENDOR, "IRBIS"));
> + dmi_match(DMI_SYS_VENDOR, "IRBIS") ||
> + dmi_match(DMI_PRODUCT_FAMILY, "ASUS BR1100FKA"));
> }
>
> static int glk_emmc_probe_slot(struct sdhci_pci_slot *slot)
next prev parent reply other threads:[~2022-09-13 6:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 21:28 Patrick Thompson
2022-09-13 6:34 ` Adrian Hunter [this message]
2022-09-16 17:58 ` Patrick Thompson
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=925b6e37-051f-927c-350a-cd767d88d72b@intel.com \
--to=adrian.hunter@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ptf@google.com \
--cc=sxm@google.com \
--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
all inboxes | Powered by JetHome®