linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Can Guo <cang@codeaurora.org>
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
Subject: [PATCH v1 0/2] Introduce a vops for resetting host controller
Date: Tue, 22 Oct 2019 21:13:26 -0700	[thread overview]
Message-ID: <1571804009-29787-1-git-send-email-cang@codeaurora.org> (raw)

Some UFS host controllers need their specific implementations of resetting
to get them into a good state. Provide a new vops to allow the platform
driver to implement this own reset operation.

Can Guo (2):
  scsi: ufs: Introduce a vops for resetting host controller
  scsi: ufs-qcom: Add reset control support for host controller

 drivers/scsi/ufs/ufs-qcom.c | 43 +++++++++++++++++++++++++++++++++++++++++++
 drivers/scsi/ufs/ufs-qcom.h |  3 +++
 drivers/scsi/ufs/ufshcd.c   | 16 ++++++++++++++++
 drivers/scsi/ufs/ufshcd.h   | 10 ++++++++++
 4 files changed, 72 insertions(+)

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


             reply	other threads:[~2019-10-23  4:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23  4:13 Can Guo [this message]
2019-10-23  4:13 ` [PATCH v1 1/2] scsi: ufs: Introduce a vops for resetting host controller Can Guo
2019-10-23 10:39   ` [EXT] " Bean Huo (beanhuo)
2019-10-29  2:11     ` cang
2019-10-31 14:44   ` Mark Salyzyn
2019-11-01  1:18     ` cang
2019-11-04 14:28   ` Avri Altman
2019-11-04 14:34     ` [EXT] " Bean Huo (beanhuo)
2019-11-04 23:46       ` cang
2019-11-04 23:44     ` cang
2019-10-23  4:13 ` [PATCH v1 2/2] scsi: ufs-qcom: Add reset control support for " Can Guo

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=1571804009-29787-1-git-send-email-cang@codeaurora.org \
    --to=cang@codeaurora.org \
    --cc=asutoshd@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 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).