On 10/28/2011 04:35 AM, Per Forlin wrote: > 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? >
host shall check the BKOPS_STATUS periodically..i will add this point.. (i think that need to check EXT_CSD register periodically.) Thanks, Jaehoon Chung > Regards, > Per > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-mmc" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
