From: Chris Ball <cjb@laptop.org>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: merez@codeaurora.org, 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 00:39:44 -0400 [thread overview]
Message-ID: <87r4slv97z.fsf@octavius.laptop.org> (raw)
In-Reply-To: <4FFA5A8C.7050005@samsung.com> (Jaehoon Chung's message of "Mon, 09 Jul 2012 13:14:04 +0900")
Hi,
On Mon, Jul 09 2012, Jaehoon Chung wrote:
> On 07/09/2012 11:48 AM, Chris Ball wrote:
>
>> Hi,
>>
>> On Sun, Jul 08 2012, Jaehoon Chung wrote:
>>>> 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.
>>
>> I'm not sure I understand. If someone has advertised MMC_CAP2_BKOPS on
>> their host, why do we also need to check for MMC_CAP2_INIT_BKOPS before
>> we enable it in the ext_csd?
>
> Actually, it didn't need to check the MMC_CAP2_INIT_BKOPS.
> Because, if MMC_CAP2_BKOPS is set, it means we want to use the bkops.
> Then we could enable in ext_csd by default.
> In the initial version, didn't add the MMC_CAP2_INIT_BKOPS.
> But some people asked me that card didn't set bkops enable bit in
> ext_csd why set enable bkops by default?
> Also others suggested the bkops enable bit should be set at user space.
Oh! I'd missed that BKOPS_EN is a one-time programmable flag; sorry.
In that case, Sebastian's previous review comments were correct, and
you should not be touching the fuse on BKOPS_EN inside the kernelspace
driver. It should only be modified from an explicit command inside
mmc-utils.
So, please have the kernel patch only bring up bkops if the flag is
already set in the ext_csd, and please submit a userspace patch to
mmc-utils for a command that sets the flag.
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-07-09 4:40 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
2012-07-09 2:48 ` Chris Ball
2012-07-09 4:14 ` Jaehoon Chung
2012-07-09 4:39 ` Chris Ball [this message]
-- 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=87r4slv97z.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=adrian.hunter@intel.com \
--cc=chuanxiao.dong@intel.com \
--cc=hanumath.prasad@stericsson.com \
--cc=jh80.chung@samsung.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.