From: Li Wei <liwei213@huawei.com>
To: robh+dt@kernel.org, mark.rutland@arm.com, xuwei5@hisilicon.com,
catalin.marinas@arm.com, will.deacon@arm.com,
vinholikatti@gmail.com, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com, khilman@baylibre.com, arnd@arndb.de,
gregory.clement@free-electrons.com,
thomas.petazzoni@free-electrons.com,
yamada.masahiro@socionext.com, riku.voipio@linaro.org,
treding@nvidia.com, krzk@kernel.org, eric@anholt.net,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-scsi@vger.kernel.org
Cc: fengbaopeng@hisilicon.com, wangyupeng4@hisilicon.com,
liwei213@huawei.com, guodong.xu@linaro.org,
lihuan41@hisilicon.com
Subject: [PATCH v4 0/5] scsi: ufs: add ufs driver code for Hisilicon Hi3660 SoC
Date: Fri, 13 Oct 2017 15:49:31 +0800 [thread overview]
Message-ID: <20171013074936.97284-1-liwei213@huawei.com> (raw)
This patchset adds driver support for UFS for Hi3660 SoC. It is verified on HiKey960 board.
Li Wei (5):
scsi: ufs: add Hisilicon ufs driver code
dt-bindings: scsi: ufs: add document for hisi-ufs
arm64: dts: add ufs dts node
arm64: defconfig: enable configs for Hisilicon ufs
arm64: defconfig: enable f2fs and squashfs
Documentation/devicetree/bindings/ufs/ufs-hisi.txt | 47 ++
arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts | 5 +
arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 19 +
arch/arm64/configs/defconfig | 11 +
drivers/scsi/ufs/Kconfig | 9 +
drivers/scsi/ufs/Makefile | 1 +
drivers/scsi/ufs/ufs-hisi.c | 625 +++++++++++++++++++++
drivers/scsi/ufs/ufs-hisi.h | 161 ++++++
8 files changed, 878 insertions(+)
create mode 100644 Documentation/devicetree/bindings/ufs/ufs-hisi.txt
create mode 100644 drivers/scsi/ufs/ufs-hisi.c
create mode 100644 drivers/scsi/ufs/ufs-hisi.h
--
2.11.0
next reply other threads:[~2017-10-13 7:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 7:49 Li Wei [this message]
2017-10-13 7:49 ` [PATCH v4 1/5] scsi: ufs: add Hisilicon ufs driver code Li Wei
2017-10-13 7:49 ` [PATCH v4 2/5] dt-bindings: scsi: ufs: add document for hisi-ufs Li Wei
[not found] ` <20171013074936.97284-3-liwei213-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-10-17 21:17 ` Rob Herring
2017-10-18 10:23 ` 答复: " liwei (CM)
2017-10-13 7:49 ` [PATCH v4 3/5] arm64: dts: add ufs dts node Li Wei
2017-10-13 7:49 ` [PATCH v4 4/5] arm64: defconfig: enable configs for Hisilicon ufs Li Wei
2017-10-13 7:49 ` [PATCH v4 5/5] arm64: defconfig: enable f2fs and squashfs Li Wei
-- strict thread matches above, loose matches on Subject: below --
2017-10-20 8:50 [PATCH v4 0/5] scsi: ufs: add ufs driver code for Hisilicon Hi3660 SoC Li Wei
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=20171013074936.97284-1-liwei213@huawei.com \
--to=liwei213@huawei.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=fengbaopeng@hisilicon.com \
--cc=gregory.clement@free-electrons.com \
--cc=guodong.xu@linaro.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=khilman@baylibre.com \
--cc=krzk@kernel.org \
--cc=lihuan41@hisilicon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.petersen@oracle.com \
--cc=riku.voipio@linaro.org \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=treding@nvidia.com \
--cc=vinholikatti@gmail.com \
--cc=wangyupeng4@hisilicon.com \
--cc=will.deacon@arm.com \
--cc=xuwei5@hisilicon.com \
--cc=yamada.masahiro@socionext.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).