From: Adrian Hunter <adrian.hunter@intel.com>
To: Avri Altman <avri.altman@wdc.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@vger.kernel.org
Cc: Ricky WU <ricky_wu@realtek.com>
Subject: Re: [PATCH v4 9/9] mmc: core: Adjust ACMD22 to SDUC
Date: Mon, 26 Aug 2024 09:34:49 +0300 [thread overview]
Message-ID: <9e2bf183-17a6-42a0-ba60-4a2384e53ca8@intel.com> (raw)
In-Reply-To: <20240825074141.3171549-10-avri.altman@wdc.com>
On 25/08/24 10:41, Avri Altman wrote:
> ACMD22 is used to verify the previously write operation. Normally, it
> returns the number of written sectors as u32. SDUC, however, returns it
> as u64. This is not a superfluous requirement, because SDUC writes may
> exceeds 2TB. For Linux mmc however, the previously write operation
> could not be more than the block layer limits, thus we make room for a
> u64 and cast the returning value to u32.
>
> Moreover, SD cards expect to be allowed the full 500msec busy period
> post write operations. This is true for standard capacity SD, and even
> more so for high volume SD cards, specifically SDUC. If CMD13 return an
> error bit, the recovery flow is entered regardless of the busy period.
> Thus, better enforce the busy period for SDUC, otherwise it might return
> a bogus bytes written.
>
> Signed-off-by: Avri Altman <avri.altman@wdc.com>
> ---
> drivers/mmc/core/block.c | 37 +++++++++++++++++++++++++++++++------
> 1 file changed, 31 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/mmc/core/block.c b/drivers/mmc/core/block.c
> index ace701273230..b73fdef1cb0d 100644
> --- a/drivers/mmc/core/block.c
> +++ b/drivers/mmc/core/block.c
> @@ -48,6 +48,7 @@
> #include <linux/mmc/sd.h>
>
> #include <linux/uaccess.h>
> +#include <asm/unaligned.h>
>
> #include "queue.h"
> #include "block.h"
> @@ -948,13 +949,20 @@ static int mmc_sd_num_wr_blocks(struct mmc_card *card, u32 *written_blocks)
> int err;
> u32 result;
> __be32 *blocks;
> -
> + u8 resp_sz;
> struct mmc_request mrq = {};
> struct mmc_command cmd = {};
> struct mmc_data data = {};
> -
> struct scatterlist sg;
>
> + /*
> + * SD cards, specifically high volume cards, expect to be allowed with the
> + * full 500msec busy period post write. Otherwise, they may not indicate
> + * correctly the number of bytes written.
> + */
> + if (mmc_card_ult_capacity(card))
> + mmc_delay(500);
To get here, it should have had to go through:
/* Try to get back to "tran" state */
if (!mmc_host_is_spi(mq->card->host) &&
(err || !mmc_ready_for_data(status)))
err = mmc_blk_fix_state(mq->card, req);
which would mean the card is not indicating "busy".
Either that is not working, or it seems like an issue
with the card, in which case it could be a card quirk
perhaps.
> +
> err = mmc_app_cmd(card->host, card);
> if (err)
> return err;
> @@ -963,7 +971,14 @@ static int mmc_sd_num_wr_blocks(struct mmc_card *card, u32 *written_blocks)
> cmd.arg = 0;
> cmd.flags = MMC_RSP_SPI_R1 | MMC_RSP_R1 | MMC_CMD_ADTC;
>
> - data.blksz = 4;
> + /*
> + * Normally, ACMD22 returns the number of written sectors as u32.
> + * SDUC, however, returns it as u64. This is not a superfluous
> + * requirement, because SDUC writes may exceed 2TB.
> + */
> + resp_sz = mmc_card_ult_capacity(card) ? 8 : 4;
> +
> + data.blksz = resp_sz;
> data.blocks = 1;
> data.flags = MMC_DATA_READ;
> data.sg = &sg;
> @@ -973,15 +988,25 @@ static int mmc_sd_num_wr_blocks(struct mmc_card *card, u32 *written_blocks)
> mrq.cmd = &cmd;
> mrq.data = &data;
>
> - blocks = kmalloc(4, GFP_KERNEL);
> + blocks = kmalloc(resp_sz, GFP_KERNEL);
> if (!blocks)
> return -ENOMEM;
>
> - sg_init_one(&sg, blocks, 4);
> + sg_init_one(&sg, blocks, resp_sz);
>
> mmc_wait_for_req(card->host, &mrq);
>
> - result = ntohl(*blocks);
> + if (mmc_card_ult_capacity(card)) {
> + u64 blocks_64 = get_unaligned_be64(blocks);
> + /*
> + * For Linux mmc however, the previously write operation could
> + * not be more than the block layer limits, thus just make room
> + * for a u64 and cast the response back to u32.
> + */
> + result = blocks_64 > UINT_MAX ? UINT_MAX : (u32)blocks_64;
> + } else {
> + result = ntohl(*blocks);
> + }
> kfree(blocks);
>
> if (cmd.error || data.error)
next prev parent reply other threads:[~2024-08-26 6:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 7:41 [PATCH v4 0/9] Add SDUC Support Avri Altman
2024-08-25 7:41 ` [PATCH v4 1/9] mmc: sd: SDUC Support Recognition Avri Altman
2024-08-25 7:41 ` [PATCH v4 2/9] mmc: sd: Add Extension memory addressing Avri Altman
2024-08-26 6:43 ` Adrian Hunter
2024-08-26 7:05 ` Avri Altman
2024-08-25 7:41 ` [PATCH v4 3/9] mmc: core: Add open-ended Ext " Avri Altman
2024-08-25 7:41 ` [PATCH v4 4/9] mmc: core: Add close-ended " Avri Altman
2024-08-26 5:32 ` Avri Altman
2024-08-26 6:51 ` Adrian Hunter
2024-08-26 7:11 ` Avri Altman
2024-08-25 7:41 ` [PATCH v4 5/9] mmc: host: Always use manual-cmd23 in SDUC Avri Altman
2024-08-25 7:41 ` [PATCH v4 6/9] mmc: host: Add close-ended Ext memory addressing Avri Altman
2024-08-25 13:33 ` Avri Altman
2024-08-26 19:31 ` kernel test robot
2024-08-26 22:28 ` kernel test robot
2024-08-25 7:41 ` [PATCH v4 7/9] mmc: core: Allow mmc erase to carry large addresses Avri Altman
2024-08-25 7:41 ` [PATCH v4 8/9] mmc: core: Add Ext memory addressing for erase Avri Altman
2024-08-25 7:41 ` [PATCH v4 9/9] mmc: core: Adjust ACMD22 to SDUC Avri Altman
2024-08-26 6:34 ` Adrian Hunter [this message]
2024-08-26 7:26 ` Avri Altman
2024-08-26 7:34 ` Adrian Hunter
2024-08-26 7:39 ` Avri Altman
2024-08-26 6:46 ` [PATCH v4 0/9] Add SDUC Support Adrian Hunter
2024-08-26 6:58 ` Avri Altman
2024-08-27 7:45 ` Avri Altman
2024-08-27 7:57 ` Adrian Hunter
2024-08-27 8:45 ` Avri Altman
2024-08-27 10:58 ` Avri Altman
2024-08-27 11:30 ` Adrian Hunter
2024-08-28 14:41 ` Ulf Hansson
2024-08-29 7:10 ` Avri Altman
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=9e2bf183-17a6-42a0-ba60-4a2384e53ca8@intel.com \
--to=adrian.hunter@intel.com \
--cc=avri.altman@wdc.com \
--cc=linux-mmc@vger.kernel.org \
--cc=ricky_wu@realtek.com \
--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