From: merez@codeaurora.org
Cc: merez@codeaurora.org, 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>,
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 v10] mmc: support BKOPS feature for eMMC
Date: Wed, 18 Jul 2012 10:13:06 -0700 (PDT) [thread overview]
Message-ID: <f0809fa3331a60eb645490cae529c723.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <50065ACE.1030802@samsung.com>
>>> +void mmc_start_bkops(struct mmc_card *card)
>>> +{
>>> + int err;
>>> + int timeout;
>>> + u8 use_busy_signal;
>>> +
>>> + BUG_ON(!card);
>>> + if (!card->ext_csd.bkops_en || !(card->host->caps2 & MMC_CAP2_BKOPS))
>>
>> Can you please explain why we need to have MMC_CAP2_BKOPS in addition to
>> card->ext_csd.bkops_en?
> We can remove the MMC_CAP2_BKOPS. but if someone didn't want to use the
> bkops feature,
> then can control with that capability.
I don't think that the host can decide not to support BKOPs if it is
enabled on the card. In such a case we might run into performance
degradation or even non functionality of the card if it needs to perform
BKOPs.
Thanks,
Maya
--
Sent by consultant of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next prev parent reply other threads:[~2012-07-18 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 19:34 [PATCH v10] mmc: support BKOPS feature for eMMC merez
2012-07-18 6:42 ` Jaehoon Chung
2012-07-18 17:13 ` merez [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-17 2:44 Jaehoon Chung
2012-07-17 9:25 ` S, Venkatraman
2012-07-17 10:17 ` Jaehoon Chung
2012-07-17 12:30 ` Adrian Hunter
2012-07-17 12:58 ` Jaehoon Chung
2012-07-18 6:16 ` Adrian Hunter
2012-07-18 6:31 ` 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=f0809fa3331a60eb645490cae529c723.squirrel@www.codeaurora.org \
--to=merez@codeaurora.org \
--cc=adrian.hunter@intel.com \
--cc=chuanxiao.dong@intel.com \
--cc=cjb@laptop.org \
--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=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.