From: Markus Niebel <list-09_linux-mmc@tqsc.de>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: linux-mmc@vger.kernel.org
Subject: Re: mmc: eMMC BKOPS status handling lock for non urgent case
Date: Mon, 08 Sep 2014 10:15:49 +0200 [thread overview]
Message-ID: <540D65B5.3010206@tqsc.de> (raw)
In-Reply-To: <5406731D.8000802@samsung.com>
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
next prev parent reply other threads:[~2014-09-08 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 16:49 mmc: eMMC BKOPS status handling lock for non urgent case Markus Niebel
2014-09-03 1:47 ` Jaehoon Chung
2014-09-08 8:15 ` Markus Niebel [this message]
2014-09-12 2:45 ` Jaehoon Chung
2014-09-15 13:13 ` Markus Niebel
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=540D65B5.3010206@tqsc.de \
--to=list-09_linux-mmc@tqsc.de \
--cc=jh80.chung@samsung.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