2022-04-20 06:58:00 +08:00
|
|
|
# SPDX-License-Identifier: GPL-2.0+
|
2012-02-29 14:41:50 +08:00
|
|
|
#
|
2022-05-12 05:25:52 +08:00
|
|
|
# Kernel configuration file for the UFS host controller drivers.
|
2012-02-29 14:41:50 +08:00
|
|
|
#
|
2013-02-26 00:14:32 +08:00
|
|
|
# Copyright (C) 2011-2013 Samsung India Software Operations
|
|
|
|
|
#
|
|
|
|
|
# Authors:
|
|
|
|
|
# Santosh Yaraganavi <santosh.sy@samsung.com>
|
|
|
|
|
# Vinayak Holikatti <h.vinayak@samsung.com>
|
2012-02-29 14:41:50 +08:00
|
|
|
|
2013-02-26 00:14:33 +08:00
|
|
|
config SCSI_UFSHCD_PCI
|
|
|
|
|
tristate "PCI bus based UFS Controller support"
|
2021-11-07 00:46:50 +08:00
|
|
|
depends on PCI
|
2020-06-14 00:50:22 +08:00
|
|
|
help
|
2021-01-07 04:55:54 +08:00
|
|
|
This selects the PCI UFS Host Controller Interface. Select this if
|
|
|
|
|
you have UFS Host Controller with PCI Interface.
|
2013-02-26 00:14:33 +08:00
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
2016-05-11 19:21:33 +08:00
|
|
|
|
|
|
|
|
config SCSI_UFS_DWC_TC_PCI
|
|
|
|
|
tristate "DesignWare pci support using a G210 Test Chip"
|
2016-09-23 19:52:52 +08:00
|
|
|
depends on SCSI_UFSHCD_PCI
|
2020-06-14 00:50:22 +08:00
|
|
|
help
|
2016-05-11 19:21:33 +08:00
|
|
|
Synopsys Test Chip is a PHY for prototyping purposes.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
2013-02-26 20:34:45 +08:00
|
|
|
|
|
|
|
|
config SCSI_UFSHCD_PLATFORM
|
|
|
|
|
tristate "Platform bus based UFS Controller support"
|
2021-01-06 12:08:22 +08:00
|
|
|
depends on HAS_IOMEM
|
2020-06-14 00:50:22 +08:00
|
|
|
help
|
2021-01-07 04:55:54 +08:00
|
|
|
This selects the UFS host controller support. Select this if
|
|
|
|
|
you have an UFS controller on Platform bus.
|
2013-02-26 20:34:45 +08:00
|
|
|
|
2021-01-07 04:55:54 +08:00
|
|
|
If you have a controller with this interface, say Y or M here.
|
2013-02-26 20:34:45 +08:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
2015-01-15 22:32:37 +08:00
|
|
|
|
2018-09-20 21:08:30 +08:00
|
|
|
config SCSI_UFS_CDNS_PLATFORM
|
|
|
|
|
tristate "Cadence UFS Controller platform driver"
|
|
|
|
|
depends on SCSI_UFSHCD_PLATFORM
|
|
|
|
|
help
|
2021-01-07 04:55:54 +08:00
|
|
|
This selects the Cadence-specific additions to UFSHCD platform driver.
|
2018-09-20 21:08:30 +08:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2016-05-11 19:21:32 +08:00
|
|
|
config SCSI_UFS_DWC_TC_PLATFORM
|
|
|
|
|
tristate "DesignWare platform support using a G210 Test Chip"
|
2023-02-10 02:49:03 +08:00
|
|
|
depends on OF && SCSI_UFSHCD_PLATFORM
|
2020-06-14 00:50:22 +08:00
|
|
|
help
|
2016-05-11 19:21:32 +08:00
|
|
|
Synopsys Test Chip is a PHY for prototyping purposes.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2015-01-15 22:32:37 +08:00
|
|
|
config SCSI_UFS_QCOM
|
2015-10-28 19:15:46 +08:00
|
|
|
tristate "QCOM specific hooks to UFS controller platform driver"
|
2015-04-11 07:11:06 +08:00
|
|
|
depends on SCSI_UFSHCD_PLATFORM && ARCH_QCOM
|
2023-01-27 05:17:31 +08:00
|
|
|
depends on GENERIC_MSI_IRQ
|
|
|
|
|
depends on RESET_CONTROLLER
|
2020-11-14 08:47:54 +08:00
|
|
|
select QCOM_SCM if SCSI_UFS_CRYPTO
|
2015-01-15 22:32:37 +08:00
|
|
|
help
|
|
|
|
|
This selects the QCOM specific additions to UFSHCD platform driver.
|
|
|
|
|
UFS host on QCOM needs some vendor specific configuration before
|
|
|
|
|
accessing the hardware which includes PHY configuration and vendor
|
|
|
|
|
specific registers.
|
|
|
|
|
|
|
|
|
|
Select this if you have UFS controller on QCOM chipset.
|
|
|
|
|
If unsure, say N.
|
2018-07-17 17:36:56 +08:00
|
|
|
|
2019-03-16 13:04:47 +08:00
|
|
|
config SCSI_UFS_MEDIATEK
|
|
|
|
|
tristate "Mediatek specific hooks to UFS controller platform driver"
|
|
|
|
|
depends on SCSI_UFSHCD_PLATFORM && ARCH_MEDIATEK
|
|
|
|
|
select PHY_MTK_UFS
|
2021-06-02 10:42:00 +08:00
|
|
|
select RESET_TI_SYSCON
|
2019-03-16 13:04:47 +08:00
|
|
|
help
|
|
|
|
|
This selects the Mediatek specific additions to UFSHCD platform driver.
|
|
|
|
|
UFS host on Mediatek needs some vendor specific configuration before
|
|
|
|
|
accessing the hardware which includes PHY configuration and vendor
|
|
|
|
|
specific registers.
|
|
|
|
|
|
|
|
|
|
Select this if you have UFS controller on Mediatek chipset.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2018-07-17 17:36:56 +08:00
|
|
|
config SCSI_UFS_HISI
|
|
|
|
|
tristate "Hisilicon specific hooks to UFS controller platform driver"
|
|
|
|
|
depends on (ARCH_HISI || COMPILE_TEST) && SCSI_UFSHCD_PLATFORM
|
2020-06-14 00:50:22 +08:00
|
|
|
help
|
2018-07-17 17:36:56 +08:00
|
|
|
This selects the Hisilicon specific additions to UFSHCD platform driver.
|
|
|
|
|
|
|
|
|
|
Select this if you have UFS controller on Hisilicon chipset.
|
|
|
|
|
If unsure, say N.
|
scsi: ufs: Add a bsg endpoint that supports UPIUs
For now, just provide an API to allocate and remove ufs-bsg node. We
will use this framework to manage ufs devices by sending UPIU
transactions.
For the time being, implements an empty bsg_request() - will add some
more functionality in coming patches.
Nonetheless, we reveal here the protocol we are planning to use: UFS
Transport Protocol Transactions. UFS transactions consist of packets
called UFS Protocol Information Units (UPIU).
There are UPIU’s defined for UFS SCSI commands, responses, data in and
data out, task management, utility functions, vendor functions,
transaction synchronization and control, and more.
By using UPIUs, we get access to the most fine-grained internals of this
protocol, and able to communicate with the device in ways, that are
sometimes beyond the capacity of the ufs driver.
Moreover and as a result, our core structure - ufs_bsg_node has a pretty
lean structure: using upiu transactions that contains the outmost
detailed info, so we don't really need complex constructs to support it.
Signed-off-by: Avri Altman <avri.altman@wdc.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Bart Van Assche <Bart.VanAssche@wdc.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
2018-10-07 22:30:35 +08:00
|
|
|
|
2022-06-03 19:05:21 +08:00
|
|
|
config SCSI_UFS_RENESAS
|
|
|
|
|
tristate "Renesas specific hooks to UFS controller platform driver"
|
|
|
|
|
depends on (ARCH_RENESAS || COMPILE_TEST) && SCSI_UFSHCD_PLATFORM
|
|
|
|
|
help
|
|
|
|
|
This selects the Renesas specific additions to UFSHCD platform driver.
|
|
|
|
|
UFS host on Renesas needs some vendor specific configuration before
|
|
|
|
|
accessing the hardware.
|
|
|
|
|
|
|
|
|
|
Select this if you have UFS controller on Renesas chipset.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2019-11-09 00:48:57 +08:00
|
|
|
config SCSI_UFS_TI_J721E
|
|
|
|
|
tristate "TI glue layer for Cadence UFS Controller"
|
|
|
|
|
depends on OF && HAS_IOMEM && (ARCH_K3 || COMPILE_TEST)
|
|
|
|
|
help
|
|
|
|
|
This selects driver for TI glue layer for Cadence UFS Host
|
|
|
|
|
Controller IP.
|
|
|
|
|
|
|
|
|
|
Selects this if you have TI platform with UFS controller.
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2020-05-28 09:16:57 +08:00
|
|
|
config SCSI_UFS_EXYNOS
|
2021-09-24 21:26:58 +08:00
|
|
|
tristate "Exynos specific hooks to UFS controller platform driver"
|
2020-05-28 09:16:57 +08:00
|
|
|
depends on SCSI_UFSHCD_PLATFORM && (ARCH_EXYNOS || COMPILE_TEST)
|
|
|
|
|
help
|
2021-09-24 21:26:58 +08:00
|
|
|
This selects the Samsung Exynos SoC specific additions to UFSHCD
|
|
|
|
|
platform driver. UFS host on Samsung Exynos SoC includes HCI and
|
|
|
|
|
UNIPRO layer, and associates with UFS-PHY driver.
|
2020-05-28 09:16:57 +08:00
|
|
|
|
2021-09-24 21:26:58 +08:00
|
|
|
Select this if you have UFS host controller on Samsung Exynos SoC.
|
2020-05-28 09:16:57 +08:00
|
|
|
If unsure, say N.
|
2022-12-09 07:43:58 +08:00
|
|
|
|
|
|
|
|
config SCSI_UFS_VARIABLE_SG_ENTRY_SIZE
|
|
|
|
|
bool
|
|
|
|
|
default y if SCSI_UFS_EXYNOS && SCSI_UFS_CRYPTO
|
2022-12-09 20:41:21 +08:00
|
|
|
|
|
|
|
|
config SCSI_UFS_SPRD
|
|
|
|
|
tristate "Unisoc specific hooks to UFS controller platform driver"
|
|
|
|
|
depends on SCSI_UFSHCD_PLATFORM && (ARCH_SPRD || COMPILE_TEST)
|
|
|
|
|
help
|
|
|
|
|
This selects the Unisoc specific additions to UFSHCD platform driver.
|
|
|
|
|
UFS host on Unisoc needs some vendor specific configuration before
|
|
|
|
|
accessing the hardware which includes PHY configuration and vendor
|
|
|
|
|
specific registers.
|
|
|
|
|
|
|
|
|
|
Select this if you have UFS controller on Unisoc chipset.
|
|
|
|
|
If unsure, say N.
|