public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Lin <shawn.lin@linux.dev>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: shawn.lin@linux.dev, linux-mmc@vger.kernel.org,
	linux-kernel@vger.kernel.org, Luke Wang <ziniu.wang_1@nxp.com>
Subject: Re: [PATCH 1/2] mmc: core: Validate UHS/DDR/HS200 timing selection for 1-bit bus width
Date: Tue, 10 Mar 2026 08:37:04 +0800	[thread overview]
Message-ID: <933a0192-3994-5c34-1981-887ff01bcec4@linux.dev> (raw)
In-Reply-To: <CAPDyKFpKBU9woEd8EfLAxuHWgyDqL=nKCPVdC687u6n-vE0duQ@mail.gmail.com>

Hi Ulf,

在 2026/03/09 星期一 22:57, Ulf Hansson 写道:
> On Fri, 6 Mar 2026 at 13:48, Shawn Lin <shawn.lin@linux.dev> wrote:
>>
>> From: Luke Wang <ziniu.wang_1@nxp.com>
>>
>> UHS/DDR/HS200 modes require at least 4-bit bus support. Host controllers
>> that lack relevant capability registers rely on paring properties provided
>> by firmware, which may incorrectly set these modes. Now that mmc_validate_host_caps()
>> has been introduced to validate such configuration violations, let's also
>> add checks for UHS/DDR/HS200 modes.
>>
>> This fixes an issue where, if the HS200/HS400 property is set while only a
>> 1-bit bus width is used, mmc_select_hs200() returns 0 without actually performing
>> the mode switch. Consequently, mmc_select_timing() proceeds without falling back to
>> mmc_select_hs(), leaving the eMMC device operating in legacy mode (26 MHz) instead
>> of switching to High Speed mode (52 MHz).
>>
>> Signed-off-by: Luke Wang <ziniu.wang_1@nxp.com>
>> [Shawn: reword the commit msg and drop HS400 change]
>> Signed-off-by: Shawn Lin <shawn.lin@linux.dev>
>> ---
>>
>>   drivers/mmc/core/host.c | 9 +++++++++
>>   1 file changed, 9 insertions(+)
>>
>> diff --git a/drivers/mmc/core/host.c b/drivers/mmc/core/host.c
>> index 88c95db..d1d4870 100644
>> --- a/drivers/mmc/core/host.c
>> +++ b/drivers/mmc/core/host.c
>> @@ -624,6 +624,15 @@ static int mmc_validate_host_caps(struct mmc_host *host)
>>                  return -EINVAL;
>>          }
>>
>> +       /* UHS/DDR/HS200 modes require at least 4-bit bus */
>> +       if (!(caps & (MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA)) &&
>> +           ((caps & (MMC_CAP_UHS | MMC_CAP_DDR)) || (caps2 & MMC_CAP2_HS200))) {
>> +               dev_warn(dev, "drop UHS/DDR/HS200 support since 1-bit bus only\n");
>> +               host->caps = caps = caps & ~(MMC_CAP_UHS | MMC_CAP_DDR);
>> +               host->caps2 = caps2 = caps2 & ~MMC_CAP2_HS200;
> 
> Hmm.
> 
> How about just updating the temporary variables, caps and caps2, here?
> 
> Then at the end of the function when we have validated all "caps", we
> can update the variables in the host, like:
> host->caps = caps;
> host->caps2 = caps2;

It looks better. Will update v2 based on your suggestion.

> 
>> +       }
>> +
>> +       /* HS400 and HS400ES modes require 8-bit bus */
>>          if (caps2 & (MMC_CAP2_HS400_ES | MMC_CAP2_HS400) &&
>>              !(caps & MMC_CAP_8_BIT_DATA) && !(caps2 & MMC_CAP2_NO_MMC)) {
>>                  dev_warn(dev, "drop HS400 support since no 8-bit bus\n");
>> --
>> 2.7.4
>>
> 
> Kind regards
> Uffe
> 

  reply	other threads:[~2026-03-10  0:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06 12:48 [PATCH 0/2] Validate and clean up UHS/DDR/HS200 timing checks Shawn Lin
2026-03-06 12:48 ` [PATCH 1/2] mmc: core: Validate UHS/DDR/HS200 timing selection for 1-bit bus width Shawn Lin
2026-03-09 14:57   ` Ulf Hansson
2026-03-10  0:37     ` Shawn Lin [this message]
2026-03-06 12:48 ` [PATCH 2/2] mmc: core: Remove checking MMC_CAP_4_BIT_DATA from mmc_host_can_uhs() Shawn Lin

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=933a0192-3994-5c34-1981-887ff01bcec4@linux.dev \
    --to=shawn.lin@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=ziniu.wang_1@nxp.com \
    /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