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" <linux-mmc@vger.kernel.org>
Cc: Ricky WU <ricky_wu@realtek.com>, Shawn Lin <shawn.lin@rock-chips.com>
Subject: Re: [PATCH v5 3/9] mmc: core: Add open-ended Ext memory addressing
Date: Wed, 4 Sep 2024 14:11:13 +0300 [thread overview]
Message-ID: <6eb58d1d-8306-4c1a-bd01-c727299aa1d0@intel.com> (raw)
In-Reply-To: <DM6PR04MB6575EAFF1D517456F9808EBFFC9C2@DM6PR04MB6575.namprd04.prod.outlook.com>
On 4/09/24 12:55, Avri Altman wrote:
>>>>> (do_data_tag ? (1 << 29) : 0);
>>>>> brq->sbc.flags = MMC_RSP_R1 | MMC_CMD_AC;
>>>>> brq->mrq.sbc = &brq->sbc;
>>>>> + } else if (mmc_card_ult_capacity(card)) {
>>>>> + mmc_blk_wait_for_idle(mq, card->host);
>>>>> + mmc_send_ext_addr(card->host, blk_rq_pos(req));
>>>>
>>>> Did you consider having mmc_start_request() send CMD22?
>>>> e.g.
>>>>
>>>> diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c index
>>>> d6c819dd68ed..22677a01c0e3 100644
>>>> --- a/drivers/mmc/core/core.c
>>>> +++ b/drivers/mmc/core/core.c
>>>> @@ -336,6 +336,9 @@ int mmc_start_request(struct mmc_host *host,
>>>> struct mmc_request *mrq) {
>>>> int err;
>>>>
>>>> + if (mrq->cmd && mrq->cmd->ext_addr)
>>>> + mmc_send_ext_addr(card->host, mrq->cmd->ext_addr);
> Oh , and yes - To state the obvious: async reqs are working fine now.
> Not sure why it wasn't when I was calling it from mmc_blk_rw_rq_prep.
>
> Thanks,
> Avri
>
>>>> +
>>> Will give it a try.
>> In the proposed form, this doesn't work.
>> Mainly because mmc_send_ext_addr eventually calls mmc_start_request by
>> itself:
>> mmc_wait_for_cmd() -> mmc_wait_for_req() -> __mmc_start_req() ->
>> mmc_start_request().
>>
>> Also, since need to call CMD22 for any address, it is ok mrq->cmd->ext_addr to be
>> 0x0, Then need it to be a little bit bulkier, e.g.:
Sorry about that
>> by adding a "check_sduc" argument to mmc_start_request, if (mrq->cmd &&
>> check_sduc)) And make it true in mmc_blk_mq_issue_rw_rq and
>> mmc_blk_read_single, false otherwise, But this seems to be an invalid option to
>> me.
Probably better to put has_ext_addr flag into mmc_command.
>>
>> And there is that thing of adding dword to mmc_command.
>>
>> What do you think?
Adding to mmc_command should be OK. If you want to save space,
it looks like 'flags' has many unused bits.
diff --git a/include/linux/mmc/core.h b/include/linux/mmc/core.h
index f0ac2e469b32..ceb521e3598f 100644
--- a/include/linux/mmc/core.h
+++ b/include/linux/mmc/core.h
@@ -17,7 +17,7 @@ struct mmc_command {
#define MMC_CMD23_ARG_REL_WR (1 << 31)
#define MMC_CMD23_ARG_TAG_REQ (1 << 29)
u32 resp[4];
- unsigned int flags; /* expected response type */
+ u16 flags; /* expected response type */
#define MMC_RSP_PRESENT (1 << 0)
#define MMC_RSP_136 (1 << 1) /* 136 bit response */
#define MMC_RSP_CRC (1 << 2) /* expect valid crc */
@@ -76,6 +76,10 @@ struct mmc_command {
*/
#define mmc_cmd_type(cmd) ((cmd)->flags & MMC_CMD_MASK)
+/* For SDUC */
+ u8 has_ext_addr;
+ u8 ext_addr;
+
unsigned int retries; /* max number of retries */
int error; /* command error */
>>
>> Thanks,
>> Avri
>>>
>>> Thanks,
>>> Avri
>>>
>>>> init_completion(&mrq->cmd_completion);
>>>>
>>>> mmc_retune_hold(host);
>>>>
>>>>> }
>>>>> }
>>>>>
>
next prev parent reply other threads:[~2024-09-04 11:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 12:23 [PATCH v5 0/9] Add SDUC Support Avri Altman
2024-08-27 12:23 ` [PATCH v5 1/9] mmc: sd: SDUC Support Recognition Avri Altman
2024-08-27 12:23 ` [PATCH v5 2/9] mmc: sd: Add Extension memory addressing Avri Altman
2024-08-27 12:23 ` [PATCH v5 3/9] mmc: core: Add open-ended Ext " Avri Altman
2024-09-03 4:56 ` Adrian Hunter
2024-09-03 8:00 ` Avri Altman
2024-09-04 8:51 ` Avri Altman
2024-09-04 9:55 ` Avri Altman
2024-09-04 11:11 ` Adrian Hunter [this message]
2024-09-04 11:17 ` Adrian Hunter
2024-08-27 12:23 ` [PATCH v5 4/9] mmc: core: Don't use close-ended rw for SDUC Avri Altman
2024-08-27 12:23 ` [PATCH v5 5/9] mmc: core: Allow mmc erase to carry large addresses Avri Altman
2024-08-27 12:23 ` [PATCH v5 6/9] mmc: core: Add Ext memory addressing for erase Avri Altman
2024-08-27 12:23 ` [PATCH v5 7/9] mmc: core: Adjust ACMD22 to SDUC Avri Altman
2024-08-27 12:23 ` [PATCH v5 8/9] mmc: core: Disable SDUC for mmc_test Avri Altman
2024-08-27 12:23 ` [PATCH v5 9/9] mmc: core: Enable SDUC 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=6eb58d1d-8306-4c1a-bd01-c727299aa1d0@intel.com \
--to=adrian.hunter@intel.com \
--cc=Avri.Altman@wdc.com \
--cc=linux-mmc@vger.kernel.org \
--cc=ricky_wu@realtek.com \
--cc=shawn.lin@rock-chips.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