From: Dolev Raviv <draviv@codeaurora.org>
To: James.Bottomley@HansenPartnership.com, hch@infradead.org
Cc: linux-scsi@vger.kernel.org, linux-scsi-owner@vger.kernel.org,
linux-arm-msm@vger.kernel.org, santoshsy@gmail.com,
Dolev Raviv <draviv@codeaurora.org>
Subject: [RFC 00/10] UFS: Power managment support
Date: Mon, 11 Aug 2014 15:40:28 +0300 [thread overview]
Message-ID: <1407760838-6406-1-git-send-email-draviv@codeaurora.org> (raw)
This patch seies introduces support for power managment in the driver
as well as vendor specific initialization - registers, clocks, voltage
regulators etc.
It includes also a rework for the init sequnce and other PM pre-
requisit such as write protection support, well-known LUN, error
handling (retries), bkops, START_STOP, and ICC levels.
Subhash Jadavani (4):
scsi: ufs: refactor query descriptor API support
scsi: support well known logical units
scsi: ufs: introduce well known logical unit in ufs
scsi: ufs: add UFS power management support
Sujit Reddy Thumma (5):
scsi: ufs: Allow vendor specific initialization
scsi: ufs: Add regulator enable support
scsi: ufs: Add clock initialization support
scsi: ufs: improve init sequence
scsi: sd: Avoid sending medium write commands if device is write
protected
Yaniv Gardi (1):
scsi: ufs: Active Power Mode - configuring bActiveICCLevel
.../devicetree/bindings/ufs/ufshcd-pltfrm.txt | 37 +
drivers/scsi/scsi_scan.c | 16 +
drivers/scsi/scsi_sysfs.c | 7 +
drivers/scsi/sd.c | 6 +-
drivers/scsi/ufs/ufs.h | 131 +-
drivers/scsi/ufs/ufshcd-pci.c | 55 +-
drivers/scsi/ufs/ufshcd-pltfrm.c | 260 ++-
drivers/scsi/ufs/ufshcd.c | 1733 ++++++++++++++++++--
drivers/scsi/ufs/ufshcd.h | 152 +-
drivers/scsi/ufs/ufshci.h | 9 +-
include/scsi/scsi.h | 1 +
include/scsi/scsi_host.h | 5 +
12 files changed, 2155 insertions(+), 257 deletions(-)
--
1.8.5.2
--
QUALCOMM ISRAEL, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
next reply other threads:[~2014-08-11 12:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 12:40 Dolev Raviv [this message]
2014-08-11 12:40 ` [RFC 01/10] scsi: ufs: Allow vendor specific initialization Dolev Raviv
2014-08-11 12:40 ` [RFC 02/10] scsi: ufs: Add regulator enable support Dolev Raviv
2014-08-11 12:40 ` [RFC 03/10] scsi: ufs: Add clock initialization support Dolev Raviv
2014-08-11 12:40 ` [RFC 04/10] scsi: ufs: refactor query descriptor API support Dolev Raviv
2014-08-11 12:40 ` [RFC 05/10] scsi: ufs: improve init sequence Dolev Raviv
2014-08-11 12:40 ` [RFC 06/10] scsi: ufs: Active Power Mode - configuring bActiveICCLevel Dolev Raviv
2014-08-11 12:40 ` [RFC 07/10] scsi: support well known logical units Dolev Raviv
2014-08-11 12:40 ` [RFC 08/10] scsi: ufs: introduce well known logical unit in ufs Dolev Raviv
2014-08-11 12:40 ` [RFC 09/10] scsi: sd: Avoid sending medium write commands if device is write protected Dolev Raviv
2014-08-19 17:30 ` Christoph Hellwig
2014-08-20 13:24 ` Martin K. Petersen
2014-08-19 17:55 ` Venkatesh Srinivas
2014-08-24 16:28 ` [RFC 09/10] " Christoph Hellwig
2014-08-11 12:40 ` [RFC 10/10] scsi: ufs: add UFS power management support Dolev Raviv
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=1407760838-6406-1-git-send-email-draviv@codeaurora.org \
--to=draviv@codeaurora.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hch@infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-scsi-owner@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=santoshsy@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).