All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: Philip Rakity <prakity@marvell.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Jae hoon Chung <jh80.chung@gmail.com>,
	Chuanxiao Dong <chuanxiao.dong@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] sdhci: always use max timeout for xfers
Date: Fri, 25 Feb 2011 21:07:22 +0100	[thread overview]
Message-ID: <20110225200722.GA2192@pengutronix.de> (raw)
In-Reply-To: <62F39533-530F-4DF4-BBC6-AF8E9AB9E751@marvell.com>

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

On Fri, Feb 25, 2011 at 10:49:25AM -0800, Philip Rakity wrote:
> v2
> 
> use define for max timeout.  remove subroutine call and just
> set the register directly

The generic description goes above the "---" line, the incremental
history of the patch usually below.

> 
> v1
> 
> The card/host controller may sometimes return a value that is
> too low and cause the h/w to timeout a transfer that would have
> worked.  Using the maximum value avoids this.
> 
> Signed-off-by: Philip Rakity <prakity@marvell.com>

What is there seems ok, but it is not enough yet. The quirks can also go
from the users.

After that, it gets even more complicated; after this patch
'host->timeout_clk' becomes obsolete which should probably cleaned up in
a later patch together with host->ops->get_timeout_clk. Hmmmm, that
needs careful auditing.

Regards,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-02-25 20:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25 17:54 [PATCH] sdhci: always use max timeout for xfers Philip Rakity
2011-02-25 18:02 ` Wolfram Sang
2011-02-25 18:12   ` Philip Rakity
2011-02-25 18:22     ` Wolfram Sang
2011-02-25 18:49       ` [PATCH V2] " Philip Rakity
2011-02-25 20:07         ` Wolfram Sang [this message]
2011-02-28  2:36           ` Jaehoon Chung

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=20110225200722.GA2192@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=chuanxiao.dong@intel.com \
    --cc=jh80.chung@gmail.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=prakity@marvell.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.