linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sujit Reddy Thumma <sthumma@codeaurora.org>
To: Vinayak Holikatti <vinholikatti@gmail.com>,
	Santosh Y <santoshsy@gmail.com>
Cc: "James E.J. Bottomley" <JBottomley@parallels.com>,
	linux-scsi@vger.kernel.org,
	Sujit Reddy Thumma <sthumma@codeaurora.org>,
	linux-arm-msm@vger.kernel.org
Subject: [PATCH V6 0/4] scsi: ufs: Improve UFS error handling
Date: Wed, 14 Aug 2013 18:43:19 +0530	[thread overview]
Message-ID: <1376486003-19925-1-git-send-email-sthumma@codeaurora.org> (raw)
In-Reply-To: <n>

The first patch fixes many issues with current task management handling
in UFSHCD driver. Others improve error handling in various scenarios.

These patches are rebased on:
[PATCH 9/9] drivers/scsi/ufs: don't check resource with devm_ioremap_resource

Changes from v5:
	- correct typo in [PATCH V5 1/4] scsi: ufs: Fix broken task ...
	- correct poll wait in [PATCH V5 2/4] scsi: ufs: Fix hardware ...
	- Included Tested-by and Reviewed-by ack's.
Changes from v4:
	- Addressed comments from Seungwon Jeon on V3
	- Updated with proper locking while ufshcd state changes
	- Retained LUN reset instead of device reset with DME_END_POINT_RESET
	- Removed error handling decisions dependent on OCS value
	- Simplified fatal error handling to abort the requests first
	  and then carry out reset.
Changes from v3:
	- Rebased.
Changes from v2:
	- [PATCH V3 1/4]: Make the task management command task tag unique
	  across SCSI/NOP/QUERY request tags.
	- [PATCH V3 3/4]: While handling device/host reset, wait for
	  pending fatal handler to return if running.
Changes from v1:
	- [PATCH V2 1/4]: Fix a race condition because of overloading
	  outstanding_tasks variable to lock the slots. A new variable
	  tm_slots_in_use will track which slots are in use by the driver.
	- [PATCH V2 2/4]: Commit text update to clarify the hardware race
	  with more details.
	- [PATCH V2 3/4]: Minor cleanup and rebase
	- [PATCH V2 4/4]: Fix a bug - sleeping in atomic context

Sujit Reddy Thumma (4):
  scsi: ufs: Fix broken task management command implementation
  scsi: ufs: Fix hardware race conditions while aborting a command
  scsi: ufs: Fix device and host reset methods
  scsi: ufs: Improve UFS fatal error handling

 drivers/scsi/ufs/ufshcd.c |  684 ++++++++++++++++++++++++++++++++-------------
 drivers/scsi/ufs/ufshcd.h |   20 +-
 2 files changed, 501 insertions(+), 203 deletions(-)

-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation.

             reply	other threads:[~2013-08-14 13:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14 13:13 Sujit Reddy Thumma [this message]
2013-08-14 13:13 ` [PATCH V6 1/4] scsi: ufs: Fix broken task management command implementation Sujit Reddy Thumma
2013-08-14 13:13 ` [PATCH V6 2/4] scsi: ufs: Fix hardware race conditions while aborting a command Sujit Reddy Thumma
2013-08-14 13:13 ` [PATCH V6 3/4] scsi: ufs: Fix device and host reset methods Sujit Reddy Thumma
2013-08-14 13:13 ` [PATCH V6 4/4] scsi: ufs: Improve UFS fatal error handling Sujit Reddy Thumma

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=1376486003-19925-1-git-send-email-sthumma@codeaurora.org \
    --to=sthumma@codeaurora.org \
    --cc=JBottomley@parallels.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=santoshsy@gmail.com \
    --cc=vinholikatti@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).