> -----Original Message----- > From: linus.ml.walleij@xxxxxxxxx [mailto:linus.ml.walleij@xxxxxxxxx] On Behalf Of > Linus Walleij > Sent: Wednesday, May 18, 2011 1:30 PM > To: Dong, Chuanxiao > Cc: Guennadi Liakhovetski; Chris Ball; David Strobach; linux-mmc@xxxxxxxxxxxxxxx; > Greg KH; horms@xxxxxxxxxxxx; damm@xxxxxxxxxxxxx; Andrei Warkentin > Subject: Re: kernel 2.6.38.6 MMC controller problem (fwd) > > 2011/5/17 Dong, Chuanxiao <chuanxiao.dong@xxxxxxxxx>: > > > mmc clock gating thread may be delayed for a long time in some scenarios. > > Since mmc_claim_host will be also used by other thread. I think this will > > possibly happen. > > That shouldn't matter? host->lock will make sure the requests are > serialized will it not? If mmc clock gating thread is scheduled when calling mmc_claim_host, host->clock is unlocked. And maybe when it is scheduled back, host was already claimed by other thread. If it is possible happened, then host->clock cannot make this serialized. > > Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
