From: Jan Glauber <jan.glauber@caviumnetworks.com>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
"Steven J. Hill" <Steven.Hill@cavium.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH 1/3] mmc: core: activate pre-erased multiple write support for sd card
Date: Fri, 27 Oct 2017 14:36:32 +0200 [thread overview]
Message-ID: <20171027123632.GA5382@hc> (raw)
In-Reply-To: <b7acd6a7-6a17-47be-5659-bf5c264d7552@rock-chips.com>
On Fri, Oct 27, 2017 at 09:46:32AM +0800, Shawn Lin wrote:
> Could you kindly try this on top of this series? And do some write test
> for the SD cards.
>
> @@ -2210,9 +2210,9 @@ static struct mmc_blk_data
> *mmc_blk_alloc_req(struct mmc_card *card,
>
> if (mmc_host_cmd23(card->host)) {
> if ((mmc_card_mmc(card) &&
> - card->csd.mmca_vsn >= CSD_SPEC_VER_3) ||
> - (mmc_card_sd(card) &&
> - card->scr.cmds & SD_SCR_CMD23_SUPPORT))
> + card->csd.mmca_vsn >= CSD_SPEC_VER_3))
> + //(mmc_card_sd(card) &&
> + //card->scr.cmds & SD_SCR_CMD23_SUPPORT))
> md->flags |= MMC_BLK_CMD23;
Did that and tested read/write to SD card, works fine on the Cavium
tn81xx arm64 board.
Feel free to add:
Tested-by: Jan Glauber <jglauber@cavium.com>
--Jan
next prev parent reply other threads:[~2017-10-27 12:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 3:40 [PATCH 1/3] mmc: core: activate pre-erased multiple write support for sd card Shawn Lin
2017-09-27 3:40 ` [PATCH 2/3] mmc: test: prepare sbc for preceding ACMD23 multiple block write Shawn Lin
2017-09-27 3:40 ` [PATCH 3/3] mmc: cavium: Add ACMD23 support for dma's multiple mode Shawn Lin
2017-09-27 13:47 ` [PATCH 1/3] mmc: core: activate pre-erased multiple write support for sd card Jan Glauber
2017-09-28 3:33 ` Shawn Lin
2017-09-28 14:29 ` Jan Glauber
2017-10-26 1:19 ` Shawn Lin
2017-10-26 10:46 ` Ulf Hansson
2017-10-26 11:03 ` Jan Glauber
2017-10-27 1:46 ` Shawn Lin
2017-10-27 12:36 ` Jan Glauber [this message]
2017-10-26 11:32 ` Adrian Hunter
2017-10-27 1:52 ` Shawn Lin
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=20171027123632.GA5382@hc \
--to=jan.glauber@caviumnetworks.com \
--cc=Steven.Hill@cavium.com \
--cc=adrian.hunter@intel.com \
--cc=jh80.chung@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=ulf.hansson@linaro.org \
--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