public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Prasanna NAVARATNA <prasanna.navaratna@gmail.com>
To: linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: sdhci: extend wait for busy signalling
Date: Tue, 10 Sep 2013 14:25:12 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130910T162234-197@post.gmane.org> (raw)
In-Reply-To: CAPDyKFppfnZ18Vev8mzaqQSDTEcDXM0eOcCM1FYKM5xSXORQQw@mail.gmail.com

> 
> I don't think this kind of protocol related code shall remain in the
> host driver. Better keep this in the protocol layer.
> 
> Moreover, most commands can be followed with status command (CMD13) to
> check for busy assertion. I believe this could be a better option to
> use from a generic point of view, since not all mmc controllers
> support hw-check for busy signalling.
> 
> In the cases were CMD13 is not allowed, there are two options to
> improve the situation.
> 1. Extend the usage of host->ops->card_busy in the protocol layer,
> thus provide the option for a host driver to implement a software busy
> check (could be by re-routing pins to GPIO for example)
> 2. MMC_CAP_WAIT_WHILE_BUSY is set by host, thus the hw support busy check.

I had implemented this patch for older version of kernel (3.4.5) and then
ported to latest kernel.
Need to check on card_busy and utilize it. I will re-work on this patch and
will update a newer version in protocol layer.

Thanks,
Prasanna NAVARATNA


      reply	other threads:[~2013-09-10 14:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05  9:23 [PATCH] mmc: sdhci: extend wait for busy signalling Prasanna NAVARATNA
2013-09-09  6:35 ` Christian Gmeiner
2013-09-09  7:41 ` Ulf Hansson
2013-09-10 14:25   ` Prasanna NAVARATNA [this message]

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=loom.20130910T162234-197@post.gmane.org \
    --to=prasanna.navaratna@gmail.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