All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: Konstantin Dorfman <kdorfman@codeaurora.org>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
	Per Forlin <per.lkml@gmail.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>,
	svenkatr@ti.com, chuanxiao.dong@intel.com
Subject: Re: [PATCH v2] mmc: support BKOPS feature for eMMC
Date: Mon, 28 Nov 2011 20:59:00 +0900	[thread overview]
Message-ID: <4ED37784.6030004@samsung.com> (raw)
In-Reply-To: <491f3d5b2d7e3949fdba902e1c98e26b.squirrel@www.codeaurora.org>

Hi Kostya

On 11/28/2011 06:39 PM, Konstantin Dorfman wrote:

> Hello Jaehoon, Per
> 
> I have experimented with eMMC v4.41 card and BKOPS feature and want to add
> info on EXT_CSD_BKOPS_EN[163] field. See below.
> 
>> Hi Per
>>
>>>>>>>>
>>>>>>>>        if (card->ext_csd.rev >= 5) {
>>>>>>>> +               /* check whether the eMMC card support BKOPS */
>>>>>>>> +               if (ext_csd[EXT_CSD_BKOPS_SUPPORT] & 0x1) {
>>>>>>>> +                       card->ext_csd.bkops = 1;
>>>>>>>> +                       card->ext_csd.bkops_en = 1;
>>>>>>> What if the card has not enabled bkops? This bit could be unset.
>>>>>>> card->ext_csd.bkops_en = ext_csd[EXT_CSD_BKOPS_EN];
>>>>>> When card is supported the bkops, bkops_en bit is set by default...
>>>>>>
>>>>> How do you know if the bkops_en is really enabled in th ext_csd?
>>>>> It could be unset in the ext_csd, right?
>>>>
>>>> In emmc4.5 spec, if card is supported the bkops, bkops_en is set by
>>>> default.
>>> If bkops_en is set by default it should be in the the ext_csd too,
>>> right?
>>> It should be safer to trust the value of ext_csd[EXT_CSD_BKOPS_EN] in
>>> this case I think.
>>
>> If we want to ensure whether bkops_en bit is set or not, your approach is
>> right.
>>
>> Best Regards,
>> Jaehoon Chung
> 
> First of all protocol state:
> ------------------------------
> 7.4.57 BKOPS_EN [163]
> This field allows the _host_ to indicate to the device if it is expected
> to periodically manually start background operations by writing to the
> BKOPS_START field.
> 
> ...In order for the device to know if host is going to periodically start
> background operations, host shall set bit 0 of BKOPS_EN (EXT_CSD byte
> [163]) to indicate that it is going to write to BKOPS_START periodically.
> The device may then delay some of its maintenance operations to when host
> writes to BKOPS_START.
> ------------------------------
> 
> My card supports BKOPS (by reading Bit 0 of BKOPS_SUPPORT (EXT_CSD byte
> [502]), but BKOPS_EN[163] is not set. So I suppose, original code to set
> BKOPS_EN[163] is needed, otherwise card will never delay its maintenance
> operations.


Ok...i will add the code for setting BKOPS_EN bit in patch-v4.
Thanks,
Jaehoon Chung

  reply	other threads:[~2011-11-28 11:59 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 [this message]
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

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=4ED37784.6030004@samsung.com \
    --to=jh80.chung@samsung.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=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.