From: Erick Shepherd <erick.shepherd@ni.com>
To: <adrian.hunter@intel.com>
Cc: <andy-ld.lu@mediatek.com>, <avri.altman@wdc.com>,
<cw9316.lee@samsung.com>, <dsimic@manjaro.org>,
<erick.shepherd@ni.com>, <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, 18 Feb 2025 12:41:56 -0600 [thread overview]
Message-ID: <20250218184156.574787-1-erick.shepherd@ni.com> (raw)
In-Reply-To: <c1863075-90bb-486a-bd25-b8ea6b2ae035@intel.com>
Sorry about that, the context for this change is that I have been
working with a DDR50 swissbit SD card that does not support tuning.
The case I'm seeing is that the first tuning times out and any
further tuning attempts cause an async page read I/O error. I used
this change to prevent the card from attempting to tune again if it
is ever reset in the case where we know tuning isn't supported.
Regards
Erick
next prev parent reply other threads:[~2025-02-18 18:42 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 [this message]
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
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=20250218184156.574787-1-erick.shepherd@ni.com \
--to=erick.shepherd@ni.com \
--cc=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=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