forked from ~ljy/RK356X_SDK_RELEASE

blame | history | patch | commit | commitdiff
hc
2024-01-03 2f7c68cb55ecb7331f2381deb497c27155f32faf 
 kernel/drivers/scsi/ufs/Kconfig
....@@ -38,7 +38,7 @@
3838 	select PM_DEVFREQ
3939 	select DEVFREQ_GOV_SIMPLE_ONDEMAND
4040 	select NLS
41
-	---help---
41
+	help
4242 	This selects the support for UFS devices in Linux, say Y and make
4343 	  sure that you know the name of your UFS host adapter (the card
4444 	  inside your computer that "speaks" the UFS protocol, also
....@@ -46,14 +46,14 @@
4646 	  The module will be called ufshcd.
4747 
4848 	  To compile this driver as a module, choose M here and read
49
-	  <file:Documentation/scsi/ufs.txt>.
49
+	  <file:Documentation/scsi/ufs.rst>.
5050 	  However, do not compile this as a module if your root file system
5151 	  (the one containing the directory /) is located on a UFS device.
5252 
5353 config SCSI_UFSHCD_PCI
5454 	tristate "PCI bus based UFS Controller support"
5555 	depends on SCSI_UFSHCD && PCI
56
-	---help---
56
+	help
5757 	This selects the PCI UFS Host Controller Interface. Select this if
5858 	you have UFS Host Controller with PCI Interface.
5959 
....@@ -64,7 +64,7 @@
6464 config SCSI_UFS_DWC_TC_PCI
6565 	tristate "DesignWare pci support using a G210 Test Chip"
6666 	depends on SCSI_UFSHCD_PCI
67
-	---help---
67
+	help
6868 	  Synopsys Test Chip is a PHY for prototyping purposes.
6969 
7070 	  If unsure, say N.
....@@ -72,7 +72,8 @@
7272 config SCSI_UFSHCD_PLATFORM
7373 	tristate "Platform bus based UFS Controller support"
7474 	depends on SCSI_UFSHCD
75
-	---help---
75
+	depends on HAS_IOMEM
76
+	help
7677 	This selects the UFS host controller support. Select this if
7778 	you have an UFS controller on Platform bus.
7879 
....@@ -80,10 +81,18 @@
8081 
8182 	  If unsure, say N.
8283 
84
+config SCSI_UFS_CDNS_PLATFORM
85
+	tristate "Cadence UFS Controller platform driver"
86
+	depends on SCSI_UFSHCD_PLATFORM
87
+	help
88
+	This selects the Cadence-specific additions to UFSHCD platform driver.
89
+
90
+	  If unsure, say N.
91
+
8392 config SCSI_UFS_DWC_TC_PLATFORM
8493 	tristate "DesignWare platform support using a G210 Test Chip"
8594 	depends on SCSI_UFSHCD_PLATFORM
86
-	---help---
95
+	help
8796 	  Synopsys Test Chip is a PHY for prototyping purposes.
8897 
8998 	  If unsure, say N.
....@@ -91,7 +100,8 @@
91100 config SCSI_UFS_QCOM
92101 	tristate "QCOM specific hooks to UFS controller platform driver"
93102 	depends on SCSI_UFSHCD_PLATFORM && ARCH_QCOM
94
-	select PHY_QCOM_UFS
103
+	select QCOM_SCM
104
+	select RESET_CONTROLLER
95105 	help
96106 	  This selects the QCOM specific additions to UFSHCD platform driver.
97107 	  UFS host on QCOM needs some vendor specific configuration before
....@@ -101,13 +111,68 @@
101111 	  Select this if you have UFS controller on QCOM chipset.
102112 	  If unsure, say N.
103113 
114
+config SCSI_UFS_MEDIATEK
115
+	tristate "Mediatek specific hooks to UFS controller platform driver"
116
+	depends on SCSI_UFSHCD_PLATFORM && ARCH_MEDIATEK
117
+	select PHY_MTK_UFS
118
+	select RESET_TI_SYSCON
119
+	help
120
+	  This selects the Mediatek specific additions to UFSHCD platform driver.
121
+	  UFS host on Mediatek needs some vendor specific configuration before
122
+	  accessing the hardware which includes PHY configuration and vendor
123
+	  specific registers.
124
+
125
+	  Select this if you have UFS controller on Mediatek chipset.
126
+
127
+	  If unsure, say N.
128
+
104129 config SCSI_UFS_HISI
105130 	tristate "Hisilicon specific hooks to UFS controller platform driver"
106131 	depends on (ARCH_HISI || COMPILE_TEST) && SCSI_UFSHCD_PLATFORM
107
-	---help---
132
+	help
108133 	  This selects the Hisilicon specific additions to UFSHCD platform driver.
109134 
110135 	  Select this if you have UFS controller on Hisilicon chipset.
136
+	  If unsure, say N.
137
+
138
+config SCSI_UFS_TI_J721E
139
+	tristate "TI glue layer for Cadence UFS Controller"
140
+	depends on OF && HAS_IOMEM && (ARCH_K3 || COMPILE_TEST)
141
+	help
142
+	  This selects driver for TI glue layer for Cadence UFS Host
143
+	  Controller IP.
144
+
145
+	  Selects this if you have TI platform with UFS controller.
146
+	  If unsure, say N.
147
+
148
+config SCSI_UFS_BSG
149
+	bool "Universal Flash Storage BSG device node"
150
+	depends on SCSI_UFSHCD
151
+	select BLK_DEV_BSGLIB
152
+	help
153
+	  Universal Flash Storage (UFS) is SCSI transport specification for
154
+	  accessing flash storage on digital cameras, mobile phones and
155
+	  consumer electronic devices.
156
+	  A UFS controller communicates with a UFS device by exchanging
157
+	  UFS Protocol Information Units (UPIUs).
158
+	  UPIUs can not only be used as a transport layer for the SCSI protocol
159
+	  but are also used by the UFS native command set.
160
+	  This transport driver supports exchanging UFS protocol information units
161
+	  with a UFS device. See also the ufshcd driver, which is a SCSI driver
162
+	  that supports UFS devices.
163
+
164
+	  Select this if you need a bsg device node for your UFS controller.
165
+	  If unsure, say N.
166
+
167
+config SCSI_UFS_EXYNOS
168
+	tristate "EXYNOS specific hooks to UFS controller platform driver"
169
+	depends on SCSI_UFSHCD_PLATFORM && (ARCH_EXYNOS || COMPILE_TEST)
170
+	help
171
+	  This selects the EXYNOS specific additions to UFSHCD platform driver.
172
+	  UFS host on EXYNOS includes HCI and UNIPRO layer, and associates with
173
+	  UFS-PHY driver.
174
+
175
+	  Select this if you have UFS host controller on EXYNOS chipset.
111176 	  If unsure, say N.
112177 
113178 config SCSI_UFS_CRYPTO
....@@ -118,3 +183,12 @@
118183 	  Enabling this makes it possible for the kernel to use the crypto
119184 	  capabilities of the UFS device (if present) to perform crypto
120185 	  operations on data being transferred to/from the device.
186
+
187
+config SCSI_UFS_HPB
188
+	bool "Support UFS Host Performance Booster"
189
+	depends on SCSI_UFSHCD
190
+	help
191
+	  The UFS HPB feature improves random read performance. It caches
192
+	  L2P (logical to physical) map of UFS to host DRAM. The driver uses HPB
193
+	  read command by piggybacking physical page number for bypassing FTL (flash
194
+	  translation layer)'s L2P address translation.