From: Dolev Raviv <draviv@codeaurora.org>
To: linux-scsi@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org, Dolev Raviv <draviv@codeaurora.org>
Subject: [PATCH V1 0/8] ufs patch siries
Date: Sun, 12 May 2013 17:23:52 +0300 [thread overview]
Message-ID: <1368368640-10167-1-git-send-email-draviv@codeaurora.org> (raw)
This patch series clusters the latest version of all the UFS patches in the
SCSI mailing list. It gives a stable functional base line for the UFS driver.
It includes the following versions:
> [PATCH 1/2] Documentation: devicetree: Add DT bindings for UFS host
> controller
> [PATCH 2/2] scsi: ufs: Fix the response UPIU length setting
> [PATCH v4 1/6] scsi: ufs: wrap the i/o access operations
> [PATCH v4 2/6] scsi: ufs: amend interrupt configuration
> [PATCH v4 3/6] scsi: ufs: fix interrupt status clears
> [PATCH v4 4/6] scsi: ufs: rework link start-up process
> [PATCH V5 1/1] scsi: ufs: Add support for sending NOP OUT UPIU
> [PATCH V4] scsi: ufs: Set fDeviceInit flag to initiate device
> initialization
But does not include:
> [PATCH v4 5/6] scsi: ufs: add dme configuration primit
> [PATCH v4 6/6] scsi: ufs: add dme control primitives
Dolev Raviv (8):
Documentation: devicetree: Add DT bindings for UFS host controller
scsi: ufs: Fix the response UPIU length setting
scsi: ufs: wrap the i/o access operations
scsi: ufs: amend interrupt configuration
scsi: ufs: fix interrupt status clears
scsi: ufs: rework link start-up process
scsi: ufs: Add support for sending NOP OUT UPIU
scsi: ufs: Set fDeviceInit flag to initiate device initialization
.../devicetree/bindings/ufs/ufshcd-pltfrm.txt | 16 +
drivers/scsi/ufs/ufs.h | 10 +-
drivers/scsi/ufs/ufshcd.c | 839 ++++++++++++++++----
drivers/scsi/ufs/ufshcd.h | 25 +-
drivers/scsi/ufs/ufshci.h | 5 +-
5 files changed, 721 insertions(+), 174 deletions(-)
create mode 100644 Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt
--
1.7.6
--
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:[~2013-05-12 14:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 14:23 Dolev Raviv [this message]
2013-05-12 14:23 ` [PATCH V1 1/8] Documentation: devicetree: Add DT bindings for UFS host controller Dolev Raviv
2013-05-12 14:23 ` [PATCH V1 2/8] scsi: ufs: Fix the response UPIU length setting Dolev Raviv
2013-05-12 14:23 ` [PATCH V1 3/8] scsi: ufs: wrap the i/o access operations Dolev Raviv
2013-05-13 4:07 ` Seungwon Jeon
2013-05-13 6:29 ` Dolev Raviv
2013-05-12 14:23 ` [PATCH V1 4/8] scsi: ufs: amend interrupt configuration Dolev Raviv
2013-05-12 14:23 ` [PATCH V1 5/8] scsi: ufs: fix interrupt status clears Dolev Raviv
2013-05-12 14:23 ` [PATCH V1 6/8] scsi: ufs: rework link start-up process Dolev Raviv
2013-05-12 14:23 ` [PATCH V1 7/8] scsi: ufs: Add support for sending NOP OUT UPIU Dolev Raviv
2013-05-12 14:24 ` [PATCH V1 8/8] scsi: ufs: Set fDeviceInit flag to initiate device initialization Dolev Raviv
-- strict thread matches above, loose matches on Subject: below --
2013-05-13 10:02 [PATCH V1 0/8] ufs patch siries Dolev Raviv
2013-05-13 11:50 ` Seungwon Jeon
2013-05-14 8:01 ` Dolev Raviv
2013-05-12 14:22 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=1368368640-10167-1-git-send-email-draviv@codeaurora.org \
--to=draviv@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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).