public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuanxiao Dong <chuanxiao.dong@intel.com>
To: linux-mmc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, cjb@laptop.org,
	arjan@linux.intel.com, alan@linux.intel.com,
	akpm@linux-foundation.org, adrian.hunter@nokia.com
Subject: [PATVH v3 0/3]mmc: set a suitable max_discard_sectors value for HC
Date: Thu, 2 Dec 2010 19:25:26 +0800	[thread overview]
Message-ID: <20101202112526.GA10358@intel.com> (raw)

Hi,
	This is the version 3 patch which set a suitable max_discard_sectors
	value for SDHCI host controller. In this patch, a new quirk is added for
	such controller.

	max_discard_sectors is a parameter of MMC driver request queue. This
	value can limit how many sectors will be passed down to host for
	erasing. The original value for this parameter is UINT_MAX which means
	there is no limitation for the count of sectors to pass down for
	erasing.

	But some SDHCI host controller cannot erase too many sectors at one
	time. It may generate a timeout interrupt since the time erasing used is
	longer than the timeout time host can wait.

	So these patches add a new quirk for such SDHCI host controller and let
	it erase only signle eraseblock each time. This will be safe for such
	SDHCI host to use.

	patch1: add a new quirk for SDHCI host controller. Also add a new
	routine mmc_set_discard_limit which is used to set max_discard_sectors
	value for such SDHCI host controller.
	patch2: set timeout control register for such SDHCI host controller.
	patch3: add this quirk for MFLD SDHCI host controller.

	Change-log:
	patch1: let mmc_set_discard_limit can return value UINT_MAX.
	patch2: no change.
	patch3: no change.

Thanks
Chuanxiao

             reply	other threads:[~2010-12-02 11:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02 11:25 Chuanxiao Dong [this message]
2010-12-07 12:06 ` [PATVH v3 0/3]mmc: set a suitable max_discard_sectors value for HC Dong, Chuanxiao

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=20101202112526.GA10358@intel.com \
    --to=chuanxiao.dong@intel.com \
    --cc=adrian.hunter@nokia.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@linux.intel.com \
    --cc=arjan@linux.intel.com \
    --cc=cjb@laptop.org \
    --cc=linux-kernel@vger.kernel.org \
    --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