From: Per Forlin <per.lkml@gmail.com>
To: linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: support BKOPS feature for eMMC
Date: Thu, 27 Oct 2011 19:35:55 +0000 (UTC) [thread overview]
Message-ID: <loom.20111027T202726-264@post.gmane.org> (raw)
In-Reply-To: 4EA93C08.9030009@samsung.com
Jaehoon Chung <jh80.chung <at> samsung.com> writes:
> +++ b/drivers/mmc/core/core.c
> @@ -238,6 +238,50 @@ mmc_start_request(struct mmc_host *host, struct
mmc_request *mrq)
> host->ops->request(host, mrq);
> }
>
> +/**
> + * mmc_start_bkops - start BKOPS for supported cards
> + * @card: MMC card to start BKOPS
> + *
> + * Start background operations whenever requested.
> + * when the urgent BKOPS bit is set in a R1 command response
> + * then background operations should be started immediately.
> +*/
This patch only starts BKOPS if it's urgent or critical. I would be preferable
to run bkops periodically and only when the card is idle to minimize the risk of
reaching URGENT.
The specs says:
-----
Hosts shall still read the full status from the BKOPS_STATUS byte periodically
and start background operations as needed.
-----
I'm thinking of checking BKOPS_STATUS when the card is idle and then run bkops
even if level is only 1 (Operations outstanding – non critical). Would this make
sense?
Regards,
Per
next prev parent reply other threads:[~2011-10-27 19:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 11:10 [PATCH] mmc: support BKOPS feature for eMMC Jaehoon Chung
2011-10-27 11:37 ` Dong, Chuanxiao
2011-10-27 12:56 ` Kyungmin Park
2011-10-27 20:33 ` Sebastian Rasmussen
2011-10-27 20:31 ` Sebastian Rasmussen
2011-10-28 3:10 ` Dong, Chuanxiao
2011-10-27 19:26 ` Sebastian Rasmussen
2011-10-28 7:25 ` Jaehoon Chung
2011-10-27 19:35 ` Per Forlin [this message]
2011-10-27 20:51 ` Sebastian Rasmussen
2011-10-27 21:47 ` Per Forlin
2011-10-27 22:25 ` Sebastian Rasmussen
2011-11-04 15:17 ` Per Forlin
2011-10-28 11:01 ` Jaehoon Chung
2011-10-28 14:42 ` Sebastian Rasmussen
2011-10-28 17:13 ` S, Venkatraman
2011-10-28 5:14 ` 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=loom.20111027T202726-264@post.gmane.org \
--to=per.lkml@gmail.com \
--cc=linux-mmc@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox