mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-13 10:56:45 +07:00
df032bf27a
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>
131 lines
4.8 KiB
Plaintext
131 lines
4.8 KiB
Plaintext
#
|
|
# Kernel configuration file for the UFS Host Controller
|
|
#
|
|
# This code is based on drivers/scsi/ufs/Kconfig
|
|
# Copyright (C) 2011-2013 Samsung India Software Operations
|
|
#
|
|
# Authors:
|
|
# Santosh Yaraganavi <santosh.sy@samsung.com>
|
|
# Vinayak Holikatti <h.vinayak@samsung.com>
|
|
#
|
|
# This program is free software; you can redistribute it and/or
|
|
# modify it under the terms of the GNU General Public License
|
|
# as published by the Free Software Foundation; either version 2
|
|
# of the License, or (at your option) any later version.
|
|
# See the COPYING file in the top-level directory or visit
|
|
# <http://www.gnu.org/licenses/gpl-2.0.html>
|
|
#
|
|
# This program is distributed in the hope that it will be useful,
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
# GNU General Public License for more details.
|
|
#
|
|
# This program is provided "AS IS" and "WITH ALL FAULTS" and
|
|
# without warranty of any kind. You are solely responsible for
|
|
# determining the appropriateness of using and distributing
|
|
# the program and assume all risks associated with your exercise
|
|
# of rights with respect to the program, including but not limited
|
|
# to infringement of third party rights, the risks and costs of
|
|
# program errors, damage to or loss of data, programs or equipment,
|
|
# and unavailability or interruption of operations. Under no
|
|
# circumstances will the contributor of this Program be liable for
|
|
# any damages of any kind arising from your use or distribution of
|
|
# this program.
|
|
|
|
config SCSI_UFSHCD
|
|
tristate "Universal Flash Storage Controller Driver Core"
|
|
depends on SCSI && SCSI_DMA
|
|
select PM_DEVFREQ
|
|
select DEVFREQ_GOV_SIMPLE_ONDEMAND
|
|
select NLS
|
|
---help---
|
|
This selects the support for UFS devices in Linux, say Y and make
|
|
sure that you know the name of your UFS host adapter (the card
|
|
inside your computer that "speaks" the UFS protocol, also
|
|
called UFS Host Controller), because you will be asked for it.
|
|
The module will be called ufshcd.
|
|
|
|
To compile this driver as a module, choose M here and read
|
|
<file:Documentation/scsi/ufs.txt>.
|
|
However, do not compile this as a module if your root file system
|
|
(the one containing the directory /) is located on a UFS device.
|
|
|
|
config SCSI_UFSHCD_PCI
|
|
tristate "PCI bus based UFS Controller support"
|
|
depends on SCSI_UFSHCD && PCI
|
|
---help---
|
|
This selects the PCI UFS Host Controller Interface. Select this if
|
|
you have UFS Host Controller with PCI Interface.
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
If unsure, say N.
|
|
|
|
config SCSI_UFS_DWC_TC_PCI
|
|
tristate "DesignWare pci support using a G210 Test Chip"
|
|
depends on SCSI_UFSHCD_PCI
|
|
---help---
|
|
Synopsys Test Chip is a PHY for prototyping purposes.
|
|
|
|
If unsure, say N.
|
|
|
|
config SCSI_UFSHCD_PLATFORM
|
|
tristate "Platform bus based UFS Controller support"
|
|
depends on SCSI_UFSHCD
|
|
---help---
|
|
This selects the UFS host controller support. Select this if
|
|
you have an UFS controller on Platform bus.
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
If unsure, say N.
|
|
|
|
config SCSI_UFS_DWC_TC_PLATFORM
|
|
tristate "DesignWare platform support using a G210 Test Chip"
|
|
depends on SCSI_UFSHCD_PLATFORM
|
|
---help---
|
|
Synopsys Test Chip is a PHY for prototyping purposes.
|
|
|
|
If unsure, say N.
|
|
|
|
config SCSI_UFS_QCOM
|
|
tristate "QCOM specific hooks to UFS controller platform driver"
|
|
depends on SCSI_UFSHCD_PLATFORM && ARCH_QCOM
|
|
select PHY_QCOM_UFS
|
|
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.
|
|
|
|
config SCSI_UFS_HISI
|
|
tristate "Hisilicon specific hooks to UFS controller platform driver"
|
|
depends on (ARCH_HISI || COMPILE_TEST) && SCSI_UFSHCD_PLATFORM
|
|
---help---
|
|
This selects the Hisilicon specific additions to UFSHCD platform driver.
|
|
|
|
Select this if you have UFS controller on Hisilicon chipset.
|
|
If unsure, say N.
|
|
|
|
config SCSI_UFS_BSG
|
|
bool "Universal Flash Storage BSG device node"
|
|
depends on SCSI_UFSHCD
|
|
select BLK_DEV_BSGLIB
|
|
help
|
|
Universal Flash Storage (UFS) is SCSI transport specification for
|
|
accessing flash storage on digital cameras, mobile phones and
|
|
consumer electronic devices.
|
|
A UFS controller communicates with a UFS device by exchanging
|
|
UFS Protocol Information Units (UPIUs).
|
|
UPIUs can not only be used as a transport layer for the SCSI protocol
|
|
but are also used by the UFS native command set.
|
|
This transport driver supports exchanging UFS protocol information units
|
|
with a UFS device. See also the ufshcd driver, which is a SCSI driver
|
|
that supports UFS devices.
|
|
|
|
Select this if you need a bsg device node for your UFS controller.
|
|
If unsure, say N.
|