All of lore.kernel.org
 help / color / mirror / Atom feed
From: Can Guo <cang@qti.qualcomm.com>
To: asutoshd@codeaurora.org, nguyenb@codeaurora.org,
	rnayak@codeaurora.org, linux-scsi@vger.kernel.org,
	kernel-team@android.com, saravanak@google.com,
	salyzyn@google.com, cang@codeaurora.org
Cc: Can Guo <cang@qti.qualcomm.com>
Subject: [PATCH v3 0/4]  UFS driver general fixes bundle 5
Date: Mon, 25 Nov 2019 22:53:29 -0800	[thread overview]
Message-ID: <1574751214-8321-1-git-send-email-cang@qti.qualcomm.com> (raw)

This bundle includes 4 general fixes for UFS driver.

Changes since v2:
- Incorporated review comments from Avri Altman, Alim Akhtar and Bean Huo.
- Updated change "scsi: ufs: Update VCCQ2 and VCCQ min/max voltage hard codes"

Changes since v1:
- Incorporated review comments from Avri Altman.
- Removed change "scsi: ufs: Add new bit field PA_INIT to UECDL register".
- Updated change "scsi: ufs: Complete pending requests in host reset and restore path".

Asutosh Das (1):
  scsi: ufs: Recheck bkops level if bkops is disabled

Can Guo (3):
  scsi: ufs: Update VCCQ2 and VCCQ min/max voltage hard codes
  scsi: ufs: Avoid messing up the compl_time_stamp of lrbs
  scsi: ufs: Complete pending requests in host reset and restore path

 drivers/scsi/ufs/ufs.h    |  6 +++---
 drivers/scsi/ufs/ufshcd.c | 31 +++++++++++++++----------------
 drivers/scsi/ufs/ufshcd.h |  2 ++
 3 files changed, 20 insertions(+), 19 deletions(-)

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project


             reply	other threads:[~2019-11-26  6:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26  6:53 Can Guo [this message]
2019-11-26  6:53 ` [PATCH v3 1/4] scsi: ufs: Recheck bkops level if bkops is disabled Can Guo
2019-11-26  6:53 ` [PATCH v3 2/4] scsi: ufs: Update VCCQ2 and VCCQ min/max voltage hard codes Can Guo
2019-11-26  7:13   ` Avri Altman
2019-11-27 12:40     ` [EXT] " Bean Huo (beanhuo)
     [not found]     ` <0101016ec4ca5743-ec27a8f4-b0cd-427b-a65e-e6a26b10d45a-000000@us-west-2.amazonses.com>
2019-12-02  7:44       ` Avri Altman
2019-11-26  6:53 ` [PATCH v3 3/4] scsi: ufs: Avoid messing up the compl_time_stamp of lrbs Can Guo
2019-11-26  6:53 ` [PATCH v3 4/4] scsi: ufs: Complete pending requests in host reset and restore path Can Guo
2019-12-10  0:47 ` [PATCH v3 0/4] UFS driver general fixes bundle 5 Martin K. Petersen

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=1574751214-8321-1-git-send-email-cang@qti.qualcomm.com \
    --to=cang@qti.qualcomm.com \
    --cc=asutoshd@codeaurora.org \
    --cc=cang@codeaurora.org \
    --cc=kernel-team@android.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nguyenb@codeaurora.org \
    --cc=rnayak@codeaurora.org \
    --cc=salyzyn@google.com \
    --cc=saravanak@google.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.