All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: "Dong, Chuanxiao" <chuanxiao.dong@intel.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	Chris Ball <cjb@laptop.org>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Hanumath Prasad <hanumath.prasad@stericsson.com>,
	Sebastian Rasmussen <sebras@gmail.com>,
	Per Forlin <per.lkml@gmail.com>,
	"svenkatr@ti.com" <svenkatr@ti.com>
Subject: Re: [PATCH v2] mmc: support BKOPS feature for eMMC
Date: Wed, 16 Nov 2011 17:36:01 +0900	[thread overview]
Message-ID: <4EC375F1.8080001@samsung.com> (raw)
In-Reply-To: <5D8008F58939784290FAB48F549751984E50599817@shsmsx502.ccr.corp.intel.com>

Hi Chuanxiao,

On 11/11/2011 03:51 PM, Dong, Chuanxiao wrote:

> Hi Jaehoon,
> 
>> -----Original Message-----
>> From: Jaehoon Chung [mailto:jh80.chung@samsung.com]
>> Sent: Wednesday, November 02, 2011 6:29 PM
>> To: linux-mmc
>> Cc: Chris Ball; Kyungmin Park; Hanumath Prasad; Sebastian Rasmussen; Per Forlin;
>> svenkatr@ti.com; Dong, Chuanxiao
>> Subject: [PATCH v2] mmc: support BKOPS feature for eMMC
>>
>> Enable eMMC background operations (BKOPS) feature.
>>
>> If URGENT_BKOPS is set after a response, note that BKOPS
>> are required. After all I/O requests are finished, run
>> BKOPS if required. Should read/write operations be requested
>> during BKOPS, first issue HPI to interrupt the ongoing BKOPS
>> and then service the request.
>>
>> If you want to enable this feature, set MMC_CAP2_BKOPS.
>>
>> Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
>> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
>> CC: Hanumath Prasad <hanumath.prasad@stericsson.com>
>>
>> ---
>> Changelog V2:
>> 	- Use EXCEPTION_STATUS instead of URGENT_BKOPS
>> 	- Add function to check Exception_status(for eMMC4.5)
>> 	- remove unnecessary code.
>>
>>  drivers/mmc/card/block.c   |    9 +++++
>>  drivers/mmc/card/queue.c   |    4 ++
>>  drivers/mmc/core/core.c    |   87
>> ++++++++++++++++++++++++++++++++++++++++++++
>>  drivers/mmc/core/mmc.c     |    9 ++++-
>>  drivers/mmc/core/mmc_ops.c |    4 ++
>>  include/linux/mmc/card.h   |   12 ++++++
>>  include/linux/mmc/core.h   |    3 ++
>>  include/linux/mmc/host.h   |    1 +
>>  include/linux/mmc/mmc.h    |   14 +++++++
>>  9 files changed, 142 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/mmc/card/block.c b/drivers/mmc/card/block.c
>> index a1cb21f..fbfb405 100644
>> --- a/drivers/mmc/card/block.c
>> +++ b/drivers/mmc/card/block.c
>> @@ -1192,6 +1192,15 @@ static int mmc_blk_issue_rw_rq(struct mmc_queue
>> *mq, struct request *rqc)
>>  		case MMC_BLK_SUCCESS:
>>  		case MMC_BLK_PARTIAL:
>>  			/*
>> +			 * Check BKOPS urgency from each R1 response
>> +			 */
>> +			if (mmc_card_mmc(card) &&
>> +				(brq->cmd.resp[0] & R1_EXCEPTION_EVENT)) {
>> +				if (mmc_is_exception_event(card,
>> +						EXT_CSD_URGENT_BKOPS))
>> +					mmc_card_set_need_bkops(card);
>> +			}
>> +			/*

> Have you thought about moving this into mmc_wait_for_req_done()? We can check if the command is a R1 or R1B or not, and set BKOPS bit in there if needed. I was just thinking if we put such code here, we may only cover the successful scenario but not for the failed cases. Putting in mmc_wait_for_req_done can cover all cases.


Thanks for comment..I will move this into mmc_wait_for_req_done..and i will test.
Then i will modify and resend the patch with your opinion

Best Regards,
Jaehoon Chung

> 
> Thanks
> Chuanxiao
> 



      parent reply	other threads:[~2011-11-16  8:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 10:28 [PATCH v2] mmc: support BKOPS feature for eMMC Jaehoon Chung
2011-11-04 18:06 ` Per Forlin
2011-11-08 12:43   ` Jae hoon Chung
2011-11-08 13:53     ` Per Forlin
2011-11-08 18:37       ` Per Forlin
2011-11-11  6:24       ` Jae hoon Chung
2011-11-11  7:55         ` Per Forlin
2011-11-14  4:18           ` Jaehoon Chung
2011-11-28  9:39             ` Konstantin Dorfman
2011-11-28 11:59               ` Jaehoon Chung
2011-11-28 12:10                 ` Kyungmin Park
2011-11-29 11:47                   ` Konstantin Dorfman
2011-11-10 22:01 ` Per Forlin
2011-11-11  4:28   ` Jae hoon Chung
2011-11-11  6:51 ` Dong, Chuanxiao
2011-11-11  7:48   ` Per Forlin
2011-11-11  8:32     ` Per Forlin
2011-11-11  8:42       ` Dong, Chuanxiao
2011-11-11 11:13         ` Per Forlin
2011-11-16  8:36   ` Jaehoon Chung [this message]

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=4EC375F1.8080001@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=chuanxiao.dong@intel.com \
    --cc=cjb@laptop.org \
    --cc=hanumath.prasad@stericsson.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=per.lkml@gmail.com \
    --cc=sebras@gmail.com \
    --cc=svenkatr@ti.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 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.