[PATCH v7 0/8] Fix error message and present UFS variant

From: Yaniv Gardi
Date: Wed Sep 02 2015 - 10:45:53 EST


V7: removed additional dead code

V6: removed dead code from ufs-qcom.c and added
calling to ufshcd_dealloc_host() in ufshcd-pltfrm.c in case
of an error after a successfull ufshcd_alloc_host()

V5: removed a redundant null check

V4: add file
Documentation/devicetree/bindings/ufs/ufs-qcom.txt
and modify the compatible strings in
Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt

V3: fixes a few minor issues.

V2: fixes a few issues of unnecessary EXPORT_SYMBOL,
types of parameters in routine definition,
build errors in case CONFIG_PM is not defined and some
other minor fixes.

Yaniv Gardi (8):
phy: qcom-ufs: fix build error when the component is built as a module
scsi: ufs-qcom: fix compilation warning if compiled as a module
scsi: ufs-qcom: update configuration option of SCSI_UFS_QCOM component
add ufshcd_get_variant ufshcd_set_variant
scsi: ufs: creates wrapper functions for vops
scsi: ufs: make the UFS variant a platform device
scsi: ufs-qcom: add debug prints for test bus
scsi: ufs-qcom: add QUniPro hardware support and power optimizations

Documentation/devicetree/bindings/ufs/ufs-qcom.txt | 57 ++
.../devicetree/bindings/ufs/ufshcd-pltfrm.txt | 4 +-
drivers/phy/phy-qcom-ufs.c | 11 +
drivers/scsi/ufs/Kconfig | 2 +-
drivers/scsi/ufs/ufs-qcom.c | 905 ++++++++++++++++-----
drivers/scsi/ufs/ufs-qcom.h | 68 +-
drivers/scsi/ufs/ufshcd-pltfrm.c | 98 +--
drivers/scsi/ufs/ufshcd-pltfrm.h | 41 +
drivers/scsi/ufs/ufshcd.c | 122 ++-
drivers/scsi/ufs/ufshcd.h | 149 +++-
10 files changed, 1119 insertions(+), 338 deletions(-)
create mode 100644 Documentation/devicetree/bindings/ufs/ufs-qcom.txt
create mode 100644 drivers/scsi/ufs/ufshcd-pltfrm.h

--
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/