linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH] mmc: block: Fix tag condition with packed writes
Date: Mon, 13 Jun 2016 09:26:48 +0300	[thread overview]
Message-ID: <575E5228.3030802@intel.com> (raw)
In-Reply-To: <7b6b85e2-4439-f091-3319-9f5ceeb72e82@rock-chips.com>

On 13/06/16 05:42, Shawn Lin wrote:
> Hi Adrian,
> 
> On 2016/6/10 21:22, Adrian Hunter wrote:
>> Apparently a cut-and-paste error, 'do_data_tag' is using 'brq' for data
>> size even though 'brq' has not been set up. Instead use blk_rq_sectors().
>>
>> Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
>> ---
>>
>>
>> Hi
>>
>> I don't know if anyone is actually using packed writes, but this is
>> something I noticed.
> 
> 
> I think if brq has not been set up, the we could meet another problem
> of checking the case of whether 4KB native sector is enabled.
> When fetching blk req from the queue, mmc_blk_issue_rw_rq already
> use brq there which is the same from your case, namely
> mq->mqrq_cur->brq, right?

Looks like that was that fixed by:

commit 3a6db10d86902491b759103ee97b2539175dd1dd
Author: Yuan, Juntao <juntao.yuan@intel.com>
Date:   Fri May 13 07:59:24 2016 +0000

    mmc: block: correct 4KB alignment check

    In sectors alignment check, brq->data.blocks means sectors of the
    previous mqrq since data.blocks for mqrq_cur hasn't been updated yet.
    data.blocks will be updated later in mmc_blk_packed_hdr_wrq_prep or
    mmc_blk_rw_rq_prep.

    static int mmc_blk_issue_rw_rq(struct mmc_queue *mq, ......
            ......
        struct mmc_blk_request *brq = &mq->mqrq_cur->brq;

    Signed-off-by: Yuan Juntao <juntao.yuan@intel.com>
    Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>

There is also another fix in the SWCMDQ changes:

	http://marc.info/?l=linux-mmc&m=146547356109940

> 
> 
> 
>>
>> Regards
>> Adrian
>>
>>
>>  drivers/mmc/card/block.c | 3 +--
>>  1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/drivers/mmc/card/block.c b/drivers/mmc/card/block.c
>> index b954516739be..aa5cfaf1fdf0 100644
>> --- a/drivers/mmc/card/block.c
>> +++ b/drivers/mmc/card/block.c
>> @@ -1834,8 +1834,7 @@ static void mmc_blk_packed_hdr_wrq_prep(struct
>> mmc_queue_req *mqrq,
>>          do_data_tag = (card->ext_csd.data_tag_unit_size) &&
>>              (prq->cmd_flags & REQ_META) &&
>>              (rq_data_dir(prq) == WRITE) &&
>> -            ((brq->data.blocks * brq->data.blksz) >=
>> -             card->ext_csd.data_tag_unit_size);
>> +            blk_rq_bytes(prq) >= card->ext_csd.data_tag_unit_size;
>>          /* Argument of CMD23 */
>>          packed_cmd_hdr[(i * 2)] =
>>              (do_rel_wr ? MMC_CMD23_ARG_REL_WR : 0) |
>>
> 
> 


  reply	other threads:[~2016-06-13  6:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-10 13:22 [PATCH] mmc: block: Fix tag condition with packed writes Adrian Hunter
2016-06-13  2:42 ` Shawn Lin
2016-06-13  6:26   ` Adrian Hunter [this message]
2016-06-13  7:32     ` Shawn Lin
2016-06-22 15:23 ` 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=575E5228.3030802@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=linux-mmc@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).