From: Kiwoong Kim <kwmad.kim@samsung.com>
To: vinholikatti@gmail.com,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: "James Bottomley" <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org, 추헌광 <hg.chu@samsung.com>
Subject: [PATCH v2 0/8] Support for Exynos specific UFS driver
Date: Sat, 08 Oct 2016 12:13:11 +0900 [thread overview]
Message-ID: <000001d22111$e6d67260$b4835720$@samsung.com> (raw)
This series of patches introduce support for Exynos specific UFS driver.
An original version of this has been applied on mass production
of commercial mobile devices.
I checked compiling with Subhash's patch
- [PATCH v3] scsi: ufshcd: fix possible unclocked register access
---
Changes from v1:
* Separate a set of newer callbacks to be added
* Make Exynos specific UFS driver compatible with a following patch
[PATCH v3] scsi: ufshcd: fix possible unclocked register access
(http://www.spinics.net/lists/linux-scsi/msg100290.html)
* Rename three of the callbacks as follows:
set_nexus_t_xfer_req -> setup_xfer_req
set_nexus_t_task_mgmt -> setup_task_mgmt
hibern8_notify -> setup_hibern8
---
Documentation/devicetree/bindings/ufs/ufs-exynos.txt | 93 +
drivers/scsi/ufs/Kconfig | 10 +
drivers/scsi/ufs/Makefile | 1 +
drivers/scsi/ufs/mphy.h | 38 +
drivers/scsi/ufs/ufs-exynos.c | 2099 ++++++++++++++++++++
drivers/scsi/ufs/ufs-exynos.h | 621 ++++++
drivers/scsi/ufs/ufshcd.c | 144 +-
drivers/scsi/ufs/ufshcd.h | 55 +
drivers/scsi/ufs/ufshci.h | 14 +-
drivers/scsi/ufs/unipro.h | 24 +
10 files changed, 3079 insertions(+), 20 deletions(-)
create mode 100644 Documentation/devicetree/bindings/ufs/ufs-exynos.txt
create mode 100644 drivers/scsi/ufs/mphy.h
create mode 100644 drivers/scsi/ufs/ufs-exynos.c
create mode 100644 drivers/scsi/ufs/ufs-exynos.h
--
1.7.9.5
--
next reply other threads:[~2016-10-08 3:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-08 3:13 Kiwoong Kim [this message]
2016-10-08 16:38 ` [PATCH v2 0/8] Support for Exynos specific UFS driver Subhash Jadavani
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='000001d22111$e6d67260$b4835720$@samsung.com' \
--to=kwmad.kim@samsung.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hg.chu@samsung.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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).