Date: Fri, 3 Dec 2010 20:13:15 +0800
From: Chuanxiao Dong <chuanxiao.dong@intel.com>
To: linux-mmc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, cjb@laptop.org, akpm@linux-foundation.org,
        arjan@linux.intel.com, alan@linux.intel.com, kmpark@infradead.org
Subject: [PATCH v2 0/4]enable Background operations and HPI feature for
	eMMC4.41 card
Message-ID: <20101203121315.GA18655@intel.com>
Reply-To: Chuanxiao Dong <chuanxiao.dong@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.19 (2009-01-05)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1524
Lines: 35

Hi,
	This is the version 2 patch to enable background operations and HPI
	feature for eMMC4.41 card. Both of these two features are optional.

	Background operations can be started when user request queue is idle. So
	each time user start to handle a new request, driver should check
	whether the card is doing BKOPS. If so, should wait until BKOPS is done
	or use a HPI command to interrupt it if eMMC card support HPI. The
	serial patches were designed as this work flow.

	This version patch only use HPI to interrupt background operation,
	didnot implement to interrupt foreground operations.

	patch1: enable background operations feature for supported eMMC card.
	patch2: start to do background operations when user request queue is
	idle. Check whether card is doing BKOPS when start a new user request.
	patch3: enable HPI for supported eMMC card.
	patch4: use HPI command to interrupt BKOPS.

	change-log:

	patch2: remove the added workqueue in the version 1 patch. This
	workqueue is used to put card in runtime suspend state. Since current
	MMC driver has not a runtime power management in card block layer, just
	remove this workqueue. Define erro response to be macro R1_ERROR_RESPONSE

	patch3: fixed community comment. Thanks for Kyungmin Park.

Thanks
Chuanxiao
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/