linux-kernel - Re: [RFC PATCH V2 2/2] mmc: allow card to disable tuning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250307211711.1289730-1-erick.shepherd@ni.com>
Date: Fri, 7 Mar 2025 15:17:11 -0600
From: Erick Shepherd <erick.shepherd@...com>
To: <adrian.hunter@...el.com>
CC: <andy-ld.lu@...iatek.com>, <avri.altman@....com>, <cw9316.lee@...sung.com>,
        <dsimic@...jaro.org>, <erick.shepherd@...com>, <keita.aihara@...y.com>,
        <linux-kernel@...r.kernel.org>, <linux-mmc@...r.kernel.org>,
        <quic_jjohnson@...cinc.com>, <ricardo@...liere.net>,
        <ulf.hansson@...aro.org>, <victor.shih@...esyslogic.com.tw>,
        <wsa+renesas@...g-engineering.com>
Subject: Re: [RFC PATCH V2 2/2] mmc: allow card to disable tuning

> 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?

Regards,
Erick