Hello Jaehoon Chung Am 03.09.2014 03:47, wrote Jaehoon Chung: > Hi, Markus > > Sorry for replying too late. > > On 08/30/2014 01:49 AM, Markus Niebel wrote: >> Hello, >> >> experimenting with the current BKOPS code we found, that when triggering >> from BKOPS_LEVEL 1, >> the status stored with mmc_card_set_doing_bkops is never reset preventing >> BKOPS from working. > In now, bkops is working for upper case than LEVEL_2 (urgent case). > Patch of LEVEL_1's case has sent at mailing, maybe you can found it.
I will look for it. > >> >> Since I'm not an expert in the mmc subsystem I ask for a hint where to look >> for completion >> and implement proper status reset. > > Could you explain to me more? If starting BKOPS with BKOPS_LEVEL 1 a switch (CMD6) without wait for completion (status polling) is issued an a status variable is set. I did'nt find a place where this status is reset. > > Best Regards, > Jaehoon Chung > >> >> Thanks in advance >> >> Markus Niebel >> Best Regards, Markus Niebel -- 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
