All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Ludovic Desroches <ludovic.desroches@atmel.com>,
	Sonic Zhang <sonic.zhang@analog.com>,
	Krzysztof Kozlowski <k.kozlowski.k@gmail.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Fabio Estevam <fabio.estevam@freescale.com>,
	Ben Dooks <ben-linux@fluff.org>,
	Hans de Goede <hdegoede@redhat.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Andi Shyti <andi.shyti@samsung.com>
Subject: Re: [RFC PATCH] mmc: remove the MMC_DATA_STREAM flag
Date: Mon, 25 Jan 2016 11:10:26 +0900	[thread overview]
Message-ID: <56A58412.8060401@samsung.com> (raw)
In-Reply-To: <87y4bgb2iu.fsf@belgarion.home>

Hi, Robert.

On 01/24/2016 02:59 AM, Robert Jarzmik wrote:
> Jaehoon Chung <jh80.chung@samsung.com> writes:
> 
>> It's not set to MMC_DATA_STREAM anywhere.
>> It seems that it had used with CMD11/20. But now CMD11/20 didn't also use.
>> I didn't know what is exactly, so i sent the patch as just RFC. 
>> If i get some comments for this, i will resend the patch after separate to each host controller.
>>
>> If MMC_DATA_STREAM can be removed, then flags of data should be then one of
>> MMC_DATA_READ and MMC_DATA_WRITE.
> The commit message won't pass checkpatch, will it ?

As you know, I mentioned if i get other comments, i will resend the patch.
This patch is RFC patch.

> 
>> --- a/drivers/mmc/card/block.c
>> +++ b/drivers/mmc/card/block.c
>> @@ -1525,13 +1525,13 @@ static void mmc_blk_rw_rq_prep(struct mmc_queue_req *mqrq,
>>  	}
>>  	if (rq_data_dir(req) == READ) {
>>  		brq->cmd.opcode = readcmd;
>> -		brq->data.flags |= MMC_DATA_READ;
>> +		brq->data.flags = MMC_DATA_READ;
> Why this chunk ? If the caller had already set some flags of its own, why
> overwrite them ? That has no connection to MMC_DATA_STREAM I can see.

If MMC_DATA_STREAM is removed, there are only two flags MMC_DATA_READ and MMC_DATA_WRITE.
Are there other flags, except MMC_DATA_READ, MMC_DATA_WRITE?
READ and WRITE can not use together.

If i missed other flags, let me know, plz. 

Best Regards,
Jaehoon Chung

> ...
>> -		brq->data.flags |= MMC_DATA_WRITE;
>> +		brq->data.flags = MMC_DATA_WRITE;
> Ditto.
>> -	brq->data.flags |= MMC_DATA_WRITE;
>> +	brq->data.flags = MMC_DATA_WRITE;
> Ditto.
> 
> ... drivers not within my area zapped ...
> 
>> diff --git a/drivers/mmc/host/pxamci.c b/drivers/mmc/host/pxamci.c
>> index ce08896..4285d3a 100644
>> --- a/drivers/mmc/host/pxamci.c
>> +++ b/drivers/mmc/host/pxamci.c
> Works for me.
> 
> Cheers.
> 


  reply	other threads:[~2016-01-25  2:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14 12:08 [RFC PATCH] mmc: remove the MMC_DATA_STREAM flag Jaehoon Chung
2016-01-15 17:01 ` Ludovic Desroches
2016-01-22  1:18   ` Jaehoon Chung
2016-01-23 17:59 ` Robert Jarzmik
2016-01-25  2:10   ` Jaehoon Chung [this message]
2016-01-27 14:16 ` 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=56A58412.8060401@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=adrian.hunter@intel.com \
    --cc=andi.shyti@samsung.com \
    --cc=ben-linux@fluff.org \
    --cc=benh@kernel.crashing.org \
    --cc=fabio.estevam@freescale.com \
    --cc=hdegoede@redhat.com \
    --cc=k.kozlowski.k@gmail.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ludovic.desroches@atmel.com \
    --cc=robert.jarzmik@free.fr \
    --cc=sonic.zhang@analog.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.