linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v2] fix device in programming state after ioctl()
@ 2019-09-05  7:53 Chaotian Jing
  2019-09-05  7:53 ` [PATCH v2 1/2] mmc: block: make the card_busy_detect() more generic Chaotian Jing
  2019-09-05  7:53 ` [PATCH v2 2/2] mmc: block: add CMD13 polling for ioctl() cmd with R1B response Chaotian Jing
  0 siblings, 2 replies; 6+ messages in thread
From: Chaotian Jing @ 2019-09-05  7:53 UTC (permalink / raw)
  To: Ulf Hansson
  Cc: Matthias Brugger, Jens Axboe, Hannes Reinecke, Chaotian Jing,
	Avri Altman, YueHaibing, Wolfram Sang, Ming Lei, Chris Boot,
	Zachary Hays, linux-mmc, linux-kernel, linux-arm-kernel,
	linux-mediatek, srv_heupstream

v2 vs v1:
	base on Avri's comment, drop the ioctl_rpmb_card_status_poll()

the user space program may access eMMC by ioctl(), after the ioctl() was
completed, it should ensure that eMMC is in transfer state, or it will
cause other thread which access eMMC got timeout error, as it assume that
card was in transfer state.

this patch add CMD13 polling for R1B command to avoid this issue.

Chaotian Jing (2):
  mmc: block: make the card_busy_detect() more generic
  mmc: block: add CMD13 polling for ioctl() cmd with R1B response

 drivers/mmc/core/block.c | 150 +++++++++++++++------------------------
 1 file changed, 57 insertions(+), 93 deletions(-)

-- 
2.18.0



^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2019-10-21 11:44 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-05  7:53 [PATCH v2] fix device in programming state after ioctl() Chaotian Jing
2019-09-05  7:53 ` [PATCH v2 1/2] mmc: block: make the card_busy_detect() more generic Chaotian Jing
2019-09-05  8:43   ` Avri Altman
2019-09-05  7:53 ` [PATCH v2 2/2] mmc: block: add CMD13 polling for ioctl() cmd with R1B response Chaotian Jing
2019-09-05  8:44   ` Avri Altman
2019-10-21 11:43   ` Ulf Hansson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).