public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuanxiao Dong <chuanxiao.dong@intel.com>
To: cjb@laptop.org
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
	alan@linux.intel.com, arjan@linux.intel.com
Subject: [PATCH v2 0/3]mmc: set a suitable max_discard_sectors value for HC
Date: Thu, 18 Nov 2010 16:59:51 +0800	[thread overview]
Message-ID: <20101118085951.GA18161@intel.com> (raw)

Hello Chris,
	  These are the version 2 patches of setting a suitable
	  max_discard_sectors value for sdhci host controller.

	  The max_discard_sectors determines how many sectors will be passed
	  down to host controller for erasing. The default value is UNIT_MAX
	  which means the block layer can pass down unlimited sectors one time
	  to host controller. But for some kinds of SDHCI host controller, like
	  MFLD SDHCI host controller cannot erase so many sectors one time. It
	  will generate a timeout interrupt since the erasing time is longer
	  than the host controller waiting timeout time. This should be a
	  hardware architecture issue.

	  So in these patches, add a new quirk to work around this. The new
	  quirk can help host controllers to set a safe max_discard_sectors value
	  for them.

	  patch1: Add a new quirk for SDHCI host controller and a new mmc
	  capability which will help mmc core layer to set a suitable
	  max_discard_sectors value for it.

	  patch2: Set the sdhci host controller timeout value to be the maximum
	  one for each erase command. This will be safe for this kind of SDHCI
	  host controller.

	  patch3: Add the new quirk to MFLD SDHCI host controller.

Thanks
Chuanxiao

             reply	other threads:[~2010-11-18  9:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18  8:59 Chuanxiao Dong [this message]
2010-11-30  7:21 ` [PATCH v2 0/3]mmc: set a suitable max_discard_sectors value for HC Dong, Chuanxiao
2010-11-30 15:59   ` Chris Ball
2010-12-01  1:03     ` 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=20101118085951.GA18161@intel.com \
    --to=chuanxiao.dong@intel.com \
    --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