Linux MultiMedia Card development
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Avri Altman <Avri.Altman@wdc.com>, Ulf Hansson <ulf.hansson@linaro.org>
Cc: "jorge@foundries.io" <jorge@foundries.io>,
	"christian.loehle@arm.com" <christian.loehle@arm.com>,
	"ricardo@foundries.io" <ricardo@foundries.io>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH] mmc: mmc_test: Add re-tuning test
Date: Fri, 15 Dec 2023 11:03:32 +0200	[thread overview]
Message-ID: <16b0353d-c892-452f-adfd-dba8fdb740e6@intel.com> (raw)
In-Reply-To: <DM6PR04MB6575F0CE62C510DB2853D404FC93A@DM6PR04MB6575.namprd04.prod.outlook.com>

On 15/12/23 10:45, Avri Altman wrote:
>> +static int mmc_test_retuning(struct mmc_test_card *test) {
>> +       if (!mmc_can_retune(test->card->host)) {
>> +               pr_info("%s: No retuning - test skipped\n",
>> +                       mmc_hostname(test->card->host));
>> +               return RESULT_UNSUP_HOST;
>> +       }
>> +
>> +       return mmc_test_rnd_perf(test, 0, 0, 8192, 30, 1);
>>  }
> I wonder if it would make sense to make a RPMB flavor for the re-tuning test?

Perhaps, but maybe that could be done from user space / mmc-utils.

> 
> Thanks,
> Avri
> 
>>
>>  /*
>> @@ -2921,6 +2934,14 @@ static const struct mmc_test_case
>> mmc_test_cases[] = {
>>                 .run = mmc_test_cmds_during_write_cmd23_nonblock,
>>                 .cleanup = mmc_test_area_cleanup,
>>         },
>> +
>> +       {
>> +               .name = "Re-tuning reliability",
>> +               .prepare = mmc_test_area_prepare,
>> +               .run = mmc_test_retuning,
>> +               .cleanup = mmc_test_area_cleanup,
>> +       },
>> +
>>  };
>>
>>  static DEFINE_MUTEX(mmc_test_lock);
>> --
>> 2.34.1
> 


  reply	other threads:[~2023-12-15  9:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14  9:09 [PATCH] mmc: mmc_test: Add re-tuning test Adrian Hunter
2023-12-15  8:45 ` Avri Altman
2023-12-15  9:03   ` Adrian Hunter [this message]
2024-01-02 16:57 ` Ulf Hansson

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=16b0353d-c892-452f-adfd-dba8fdb740e6@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=Avri.Altman@wdc.com \
    --cc=christian.loehle@arm.com \
    --cc=jorge@foundries.io \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ricardo@foundries.io \
    --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