All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: merez@codeaurora.org
Cc: Chris Ball <cjb@laptop.org>,
	Jaehoon Chung <jh80.chung@samsung.com>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Hanumath Prasad <hanumath.prasad@stericsson.com>,
	Per FORLIN <per.forlin@stericsson.com>,
	Sebastian Rasmussen <sebras@gmail.com>,
	"Dong, Chuanxiao" <chuanxiao.dong@intel.com>,
	"svenkatr@ti.com" <svenkatr@ti.com>,
	Saugata Das <saugata.das@linaro.org>,
	Konstantin Dorfman <kdorfman@codeaurora.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Ulf Hansson <ulf.hansson@stericsson.com>
Subject: Re: [PATCH v9] mmc: support BKOPS feature for eMMC
Date: Mon, 09 Jul 2012 11:34:28 +0900	[thread overview]
Message-ID: <4FFA4334.7010904@samsung.com> (raw)
In-Reply-To: <f7d81e8e689ba8603f1cdcffc4722ebb.squirrel@www.codeaurora.org>

Hi, 

On 07/08/2012 07:13 PM, merez@codeaurora.org wrote:

> 
> On Fri, July 6, 2012 9:47 am, Chris Ball wrote:
>> Hi,
>>
>> On Fri, Jun 08 2012, Jaehoon Chung wrote:
>>> 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 BKOPS-STATUS is upper than LEVEL2, need to check until clear
>>> the BKOPS-STATUS vaule.
>>>
>>> If you want to enable this feature, set MMC_CAP2_BKOPS.
>>> And if you want to set the BKOPS_EN bit in ext_csd register,
>>> use the MMC_CAP2_INIT_BKOPS.
>> [..]
>>> diff --git a/include/linux/mmc/host.h b/include/linux/mmc/host.h
>>> index 0707d22..d23caf2 100644
>>> --- a/include/linux/mmc/host.h
>>> +++ b/include/linux/mmc/host.h
>>> @@ -238,6 +238,8 @@ struct mmc_host {
>>>  #define MMC_CAP2_BROKEN_VOLTAGE	(1 << 7)	/* Use the broken voltage */
>>>  #define MMC_CAP2_DETECT_ON_ERR	(1 << 8)	/* On I/O err check card
>>> removal */
>>>  #define MMC_CAP2_HC_ERASE_SZ	(1 << 9)	/* High-capacity erase size */
>>> +#define MMC_CAP2_INIT_BKOPS	(1 << 10)	/* To enable BKOPS */
>>> +#define MMC_CAP2_BKOPS		(1 << 11)	/* BKOPS supported */
>>
>> Can we have a better explanation of how these capabilities are supposed
>> to be used, and why it's necessary to have two of them?  Why would you
>> set one but not the other?
>>
>> Thanks,
>>
>> - Chris.
>> --
>> Chris Ball   <cjb@laptop.org>   <http://printf.net/>
>> One Laptop Per Child
>>
> I think MMC_CAP2_BKOPS should be removed. If the card BKOPs were already
> enabled, the host must support BKOPs. Therefore, in mmc_start_bkops we
> should check only if card->ext_csd.bkops_en is set.

If bkops bit is set, it means that use the bkops by default.
If somebody didn't want to use the bkops, then just didn't set the MMC_CAP2_BKOPS.
And eMMC card's BKOPS bit should not be set,
then we can set the BKOPS support with switch command.
For this, MMC_CAP2_INIT_BKOPS is added.
In my case, didn't set the bkops enable bit at first time.
So need to set bkops enable bit with switch command.

As Maya's mentioned, if we use the bkops by default, we can remove the MMC_CAP2_BKOPS2.

Best Regards,
Jaehoon Chung

> 
> Thanks,
> Maya
> 
> 



  reply	other threads:[~2012-07-09  2:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08  4:39 [PATCH v9] mmc: support BKOPS feature for eMMC Jaehoon Chung
2012-06-13 12:40 ` Dong, Chuanxiao
     [not found]   ` <17296D9F8FF2234F831FC3DF505A87A90FEA11E5@SHSMSX102.ccr.corp.intel.com >
2012-06-14 14:49     ` Konstantin Dorfman
2012-06-15  3:00   ` Jaehoon Chung
2012-06-13 13:53 ` S, Venkatraman
2012-06-14  8:44   ` merez
2012-06-15  4:29   ` Jaehoon Chung
2012-06-14 13:46 ` Adrian Hunter
2012-06-14 14:58   ` Konstantin Dorfman
2012-07-12  5:02   ` Jaehoon Chung
2012-07-12  6:00     ` Adrian Hunter
2012-07-12  6:50       ` Jaehoon Chung
     [not found] ` <4FD88B7D.3000600@codeaurora.org>
2012-06-15  4:19   ` Jaehoon Chung
2012-06-15  6:10     ` Subhash Jadavani
2012-07-06 16:47 ` Chris Ball
2012-07-08 10:13   ` merez
2012-07-09  2:34     ` Jaehoon Chung [this message]
2012-07-09  2:48       ` Chris Ball
2012-07-09  4:14         ` Jaehoon Chung
2012-07-09  4:39           ` Chris Ball
  -- strict thread matches above, loose matches on Subject: below --
2012-06-12 10:58 merez
2012-06-13  3:07 ` Jaehoon Chung
2012-06-13  6:18   ` merez

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=4FFA4334.7010904@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=adrian.hunter@intel.com \
    --cc=chuanxiao.dong@intel.com \
    --cc=cjb@laptop.org \
    --cc=hanumath.prasad@stericsson.com \
    --cc=kdorfman@codeaurora.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=merez@codeaurora.org \
    --cc=per.forlin@stericsson.com \
    --cc=saugata.das@linaro.org \
    --cc=sebras@gmail.com \
    --cc=svenkatr@ti.com \
    --cc=ulf.hansson@stericsson.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.