From: Adrian Hunter <adrian.hunter@intel.com>
To: Erick Shepherd <erick.shepherd@ni.com>
Cc: <andy-ld.lu@mediatek.com>, <avri.altman@wdc.com>,
<cw9316.lee@samsung.com>, <dsimic@manjaro.org>,
<keita.aihara@sony.com>, <linux-kernel@vger.kernel.org>,
<linux-mmc@vger.kernel.org>, <quic_jjohnson@quicinc.com>,
<ricardo@marliere.net>, <ulf.hansson@linaro.org>,
<victor.shih@genesyslogic.com.tw>,
<wsa+renesas@sang-engineering.com>
Subject: Re: [RFC PATCH V2 2/2] mmc: allow card to disable tuning
Date: Tue, 11 Mar 2025 17:20:01 +0200 [thread overview]
Message-ID: <65238f8f-46b8-41f2-a992-0d1a150ae8c1@intel.com> (raw)
In-Reply-To: <20250307211711.1289730-1-erick.shepherd@ni.com>
On 7/03/25 23:17, Erick Shepherd wrote:
>> Does it tuning at all? Maybe MMC_QUIRK_NO_UHS_DDR50_TUNING is a better
>> name, then at the top of mmc_execute_tuning()
>
>> if ((card->quirks & MMC_QUIRK_NO_UHS_DDR50_TUNING) &&
>> host->ios->timing == MMC_TIMING_UHS_DDR50)
>> return 0;
>
> The card doesn't need to tune at all so I think this would work for us.
> I'm not very familiar with using card quirks. What would be the best
> way to set MMC_QUIRK_NO_UHS_DDR50_TUNING? Would it be set based on the
> model of the card or should it be set after the initial tuning times
> out?
Based on the model of the card i.e. add a new entry to mmc_sd_fixups[]
next prev parent reply other threads:[~2025-03-11 15:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 21:08 [RFC PATCH V2 1/2] mmc: Update sdhci tune function to return errors Erick Shepherd
2025-02-06 21:08 ` [RFC PATCH V2 2/2] mmc: allow card to disable tuning Erick Shepherd
2025-02-15 1:08 ` Adrian Hunter
2025-02-18 18:41 ` Erick Shepherd
2025-03-06 14:01 ` Adrian Hunter
2025-03-07 17:45 ` Erick Shepherd
2025-03-07 18:44 ` Adrian Hunter
2025-03-07 21:17 ` Erick Shepherd
2025-03-11 15:20 ` Adrian Hunter [this message]
2025-03-13 16:32 ` Erick Shepherd
2025-02-06 22:34 ` [RFC PATCH V2 1/2] mmc: Update sdhci tune function to return errors Ricardo B. Marlière
2025-02-15 1:05 ` Adrian Hunter
2025-02-18 18:41 ` Erick Shepherd
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=65238f8f-46b8-41f2-a992-0d1a150ae8c1@intel.com \
--to=adrian.hunter@intel.com \
--cc=andy-ld.lu@mediatek.com \
--cc=avri.altman@wdc.com \
--cc=cw9316.lee@samsung.com \
--cc=dsimic@manjaro.org \
--cc=erick.shepherd@ni.com \
--cc=keita.aihara@sony.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=ricardo@marliere.net \
--cc=ulf.hansson@linaro.org \
--cc=victor.shih@genesyslogic.com.tw \
--cc=wsa+renesas@sang-engineering.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