| /kernel/linux/linux-5.10/drivers/scsi/ufs/ |
| D | ufs-exynos.c | 3 * UFS Host Controller driver for Exynos specific extensions
23 #include "ufs-exynos.h"
99 * UFS Protector registers
110 static void exynos_ufs_auto_ctrl_hcc(struct exynos_ufs *ufs, bool en);
111 static void exynos_ufs_ctrl_clkstop(struct exynos_ufs *ufs, bool en);
113 static inline void exynos_ufs_enable_auto_ctrl_hcc(struct exynos_ufs *ufs) in exynos_ufs_enable_auto_ctrl_hcc() argument
115 exynos_ufs_auto_ctrl_hcc(ufs, true); in exynos_ufs_enable_auto_ctrl_hcc()
118 static inline void exynos_ufs_disable_auto_ctrl_hcc(struct exynos_ufs *ufs) in exynos_ufs_disable_auto_ctrl_hcc() argument
120 exynos_ufs_auto_ctrl_hcc(ufs, false); in exynos_ufs_disable_auto_ctrl_hcc()
124 struct exynos_ufs *ufs, u32 *val) in exynos_ufs_disable_auto_ctrl_hcc_save() argument
[all …]
|
| D | Kconfig | 2 # Kernel configuration file for the UFS Host Controller
4 # This code is based on drivers/scsi/ufs/Kconfig
42 This selects the support for UFS devices in Linux, say Y and make
43 sure that you know the name of your UFS host adapter (the card
44 inside your computer that "speaks" the UFS protocol, also
45 called UFS Host Controller), because you will be asked for it.
49 <file:Documentation/scsi/ufs.rst>.
51 (the one containing the directory /) is located on a UFS device.
54 tristate "PCI bus based UFS Controller support"
57 This selects the PCI UFS Host Controller Interface. Select this if
[all …]
|
| D | ufs_quirks.h | 22 * ufs_dev_fix - ufs device quirk info
23 * @card: ufs card details
42 * Some vendor's UFS device sends back to back NACs for the DL data frames
44 * such UFS devices send back to back NAC without waiting for new
53 * raised by UFS controller.
60 * If DL NAC error is seen multiple times with some vendor's UFS devices then
67 * Few Toshiba UFS device models advertise RX_MIN_ACTIVATETIME_CAPABILITY as
69 * from UFS device.
76 * It seems some UFS devices may keep drawing more than sleep current
77 * (atleast for 500us) from UFS rails (especially from VCCQ rail).
[all …]
|
| /kernel/linux/linux-6.6/drivers/ufs/host/ |
| D | ufs-exynos.c | 3 * UFS Host Controller driver for Exynos specific extensions
21 #include <ufs/ufshcd.h>
23 #include <ufs/ufshci.h>
24 #include <ufs/unipro.h>
26 #include "ufs-exynos.h"
82 /* FSYS UFS Shareability */
144 * UFS Protector registers
155 static void exynos_ufs_auto_ctrl_hcc(struct exynos_ufs *ufs, bool en);
156 static void exynos_ufs_ctrl_clkstop(struct exynos_ufs *ufs, bool en);
158 static inline void exynos_ufs_enable_auto_ctrl_hcc(struct exynos_ufs *ufs) in exynos_ufs_enable_auto_ctrl_hcc() argument
[all …]
|
| D | Kconfig | 3 # Kernel configuration file for the UFS host controller drivers.
12 tristate "PCI bus based UFS Controller support"
15 This selects the PCI UFS Host Controller Interface. Select this if
16 you have UFS Host Controller with PCI Interface.
31 tristate "Platform bus based UFS Controller support"
34 This selects the UFS host controller support. Select this if
35 you have an UFS controller on Platform bus.
42 tristate "Cadence UFS Controller platform driver"
58 tristate "QCOM specific hooks to UFS controller platform driver"
65 UFS host on QCOM needs some vendor specific configuration before
[all …]
|
| D | ufs-exynos.h | 3 * UFS Host Controller driver for Exynos specific extensions
102 #define UNIPRO_PCLK_PERIOD(ufs) (NSEC_PER_SEC / ufs->pclk_rate) argument
167 int (*drv_init)(struct device *dev, struct exynos_ufs *ufs);
168 int (*pre_link)(struct exynos_ufs *ufs);
169 int (*post_link)(struct exynos_ufs *ufs);
170 int (*pre_pwr_change)(struct exynos_ufs *ufs,
172 int (*post_pwr_change)(struct exynos_ufs *ufs,
174 int (*pre_hce_enable)(struct exynos_ufs *ufs);
175 int (*post_hce_enable)(struct exynos_ufs *ufs);
226 #define for_each_ufs_rx_lane(ufs, i) \ argument
[all …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-driver-ufs | 6 UFS host controller. A value of '0' means auto-hibernate is not
8 idle time before the UFS host controller will autonomously put
12 maximum value of 102300000. Refer to the UFS Host Controller
16 What: /sys/bus/platform/devices/*.ufs/device_descriptor/device_type
19 Description: This file shows the device type. This is one of the UFS
21 the descriptor could be found at UFS specifications 2.1.
26 What: /sys/bus/platform/devices/*.ufs/device_descriptor/device_class
29 Description: This file shows the device class. This is one of the UFS
31 the descriptor could be found at UFS specifications 2.1.
36 What: /sys/bus/platform/devices/*.ufs/device_descriptor/device_sub_class
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/phy/ |
| D | qcom,sc8280xp-qmp-ufs-phy.yaml | 4 $id: http://devicetree.org/schemas/phy/qcom,sc8280xp-qmp-ufs-phy.yaml#
7 title: Qualcomm QMP PHY controller (UFS, SC8280XP)
14 controllers on Qualcomm chipsets, such as, PCIe, UFS, and USB.
19 - qcom,msm8996-qmp-ufs-phy
20 - qcom,msm8998-qmp-ufs-phy
21 - qcom,sa8775p-qmp-ufs-phy
22 - qcom,sc8180x-qmp-ufs-phy
23 - qcom,sc8280xp-qmp-ufs-phy
24 - qcom,sdm845-qmp-ufs-phy
25 - qcom,sm6115-qmp-ufs-phy
[all …]
|
| /kernel/linux/linux-6.6/Documentation/scsi/ |
| D | ufs.rst | 11 2. UFS Architecture Overview
13 2.2 UFS Transport Protocol (UTP) layer
14 2.3 UFS Interconnect (UIC) Layer
16 3.1 UFS controller initialization
18 3.3 UFS error handling
21 5. UFS Reference Clock Frequency configuration
27 Universal Flash Storage (UFS) is a storage specification for flash devices.
31 is defined by JEDEC Solid State Technology Association. UFS is based
32 on the MIPI M-PHY physical layer standard. UFS uses MIPI M-PHY as the
35 The main goals of UFS are to provide:
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-driver-ufs | 6 UFS host controller. A value of '0' means auto-hibernate is not
8 idle time before the UFS host controller will autonomously put
12 maximum value of 102300000. Refer to the UFS Host Controller
18 Description: This file shows the device type. This is one of the UFS
20 the descriptor could be found at UFS specifications 2.1.
27 Description: This file shows the device class. This is one of the UFS
29 the descriptor could be found at UFS specifications 2.1.
36 Description: This file shows the UFS storage subclass. This is one of
37 the UFS device descriptor parameters. The full information
38 about the descriptor could be found at UFS specifications 2.1.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/scsi/ |
| D | ufs.rst | 11 2. UFS Architecture Overview
13 2.2 UFS Transport Protocol(UTP) layer
14 2.3 UFS Interconnect(UIC) Layer
16 3.1 UFS controller initialization
18 3.3 UFS error handling
25 Universal Flash Storage(UFS) is a storage specification for flash devices.
29 is defined by JEDEC Solid State Technology Association. UFS is based
30 on MIPI M-PHY physical layer standard. UFS uses MIPI M-PHY as the
33 The main goals of UFS is to provide:
37 For UFS version 1.0 and 1.1 the target performance is as follows:
[all …]
|
| /kernel/linux/linux-6.6/drivers/ufs/core/ |
| D | Kconfig | 3 # Kernel configuration file for the UFS Host Controller core.
15 Universal Flash Storage (UFS) is SCSI transport specification for
18 A UFS controller communicates with a UFS device by exchanging
19 UFS Protocol Information Units (UPIUs).
21 but are also used by the UFS native command set.
22 This transport driver supports exchanging UFS protocol information units
23 with a UFS device. See also the ufshcd driver, which is a SCSI driver
24 that supports UFS devices.
26 Select this if you need a bsg device node for your UFS controller.
30 bool "UFS Crypto Engine Support"
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/ufs/ |
| D | ufs-hisi.txt | 1 * Hisilicon Universal Flash Storage (UFS) Host Controller
3 UFS nodes are defined to describe on-chip UFS hardware macro.
4 Each UFS Host Controller should have its own node.
8 "hisilicon,hi3660-ufs", "jedec,ufs-1.1" for hisi ufs
10 "hisilicon,hi3670-ufs", "jedec,ufs-2.1" for hisi ufs
12 - reg : should contain UFS register address space & UFS SYS CTRL register address,
23 - reset-names : reset node register, the "rst" corresponds to reset the whole UFS IP.
27 ufs: ufs@ff3b0000 {
28 compatible = "hisilicon,hi3660-ufs", "jedec,ufs-1.1";
30 /* 1: UFS SYS CTRL */
|
| D | ufshcd-pltfrm.txt | 1 * Universal Flash Storage (UFS) Host Controller
3 UFSHC nodes are defined to describe on-chip UFS host controllers.
4 Each UFS controller instance should have its own node.
7 - compatible : must contain "jedec,ufs-1.1" or "jedec,ufs-2.0"
12 "qcom,msm8994-ufshc", "qcom,ufshc", "jedec,ufs-2.0"
13 "qcom,msm8996-ufshc", "qcom,ufshc", "jedec,ufs-2.0"
14 "qcom,msm8998-ufshc", "qcom,ufshc", "jedec,ufs-2.0"
15 "qcom,sdm845-ufshc", "qcom,ufshc", "jedec,ufs-2.0"
16 "qcom,sm8150-ufshc", "qcom,ufshc", "jedec,ufs-2.0"
17 - interrupts : <interrupt mapping for UFS host controller IRQ>
[all …]
|
| D | ufs-mediatek.txt | 1 * Mediatek Universal Flash Storage (UFS) Host Controller
3 UFS nodes are defined to describe on-chip UFS hardware macro.
4 Each UFS Host Controller should have its own node.
6 To bind UFS PHY with UFS host controller, the controller node should
7 contain a phandle reference to UFS M-PHY node.
9 Required properties for UFS nodes:
11 "mediatek,mt8183-ufshci" for MediaTek UFS host controller
13 "mediatek,mt8192-ufshci" for MediaTek UFS host controller
15 - reg : Address and length of the UFS register set.
19 order as the clocks property. "ufs" is mandatory.
[all …]
|
| D | ufs-qcom.txt | 1 * Qualcomm Technologies Inc Universal Flash Storage (UFS) PHY
3 UFSPHY nodes are defined to describe on-chip UFS PHY hardware macro.
4 Each UFS PHY node should have its own node.
6 To bind UFS PHY with UFS host controller, the controller node should
7 contain a phandle reference to UFS PHY node.
11 "qcom,ufs-phy-qmp-20nm" for 20nm ufs phy,
12 "qcom,ufs-phy-qmp-14nm" for legacy 14nm ufs phy,
13 "qcom,msm8996-ufs-phy-qmp-14nm" for 14nm ufs phy
30 - vddp-ref-clk-supply : phandle to UFS device ref_clk pad power supply
32 - resets : specifies the PHY reset in the UFS controller
[all …]
|
| D | ti,j721e-ufs.yaml | 4 $id: http://devicetree.org/schemas/ufs/ti,j721e-ufs.yaml#
7 title: TI J721e UFS Host Controller Glue Driver
15 - const: ti,j721e-ufs
19 description: address of TI UFS glue registers
49 "^ufs@[0-9a-f]+$":
52 Cadence UFS controller node must be the child node. Refer
53 Documentation/devicetree/bindings/ufs/cdns,ufshc.txt for binding
67 ufs-wrapper@4e80000 {
68 compatible = "ti,j721e-ufs";
79 ufs@4000 {
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/ufs/ |
| D | samsung,exynos-ufs.yaml | 4 $id: http://devicetree.org/schemas/ufs/samsung,exynos-ufs.yaml#
7 title: Samsung SoC series UFS host controller
13 Each Samsung UFS host controller instance should have its own node.
16 - $ref: ufs-common.yaml
21 - samsung,exynos7-ufs
22 - samsung,exynosautov9-ufs
23 - samsung,exynosautov9-ufs-vh
24 - tesla,fsd-ufs
31 - description: UFS protector register
42 - description: ufs link core clock
[all …]
|
| D | hisilicon,ufs.yaml | 4 $id: http://devicetree.org/schemas/ufs/hisilicon,ufs.yaml#
7 title: HiSilicon Universal Flash Storage (UFS) Controller
12 # Select only our matches, not all jedec,ufs
18 - hisilicon,hi3660-ufs
19 - hisilicon,hi3670-ufs
24 - $ref: ufs-common.yaml
30 - const: hisilicon,hi3660-ufs
31 - const: jedec,ufs-1.1
34 - hisilicon,hi3670-ufs
35 - const: jedec,ufs-2.1
[all …]
|
| D | sprd,ums9620-ufs.yaml | 4 $id: http://devicetree.org/schemas/ufs/sprd,ums9620-ufs.yaml#
7 title: Unisoc Universal Flash Storage (UFS) Controller
13 - $ref: ufs-common.yaml
17 const: sprd,ums9620-ufs
43 sprd,ufs-anlg-syscon:
45 description: phandle of syscon used to control ufs analog regs.
65 ufs: ufs@22000000 {
66 compatible = "sprd,ums9620-ufs";
77 sprd,ufs-anlg-syscon = <&anlg_phy_g12_regs>;
|
| /kernel/linux/linux-6.6/include/ufs/ |
| D | ufs_quirks.h | 22 * ufs_dev_quirk - ufs device quirk info
23 * @card: ufs card details
33 * Some vendor's UFS device sends back to back NACs for the DL data frames
35 * such UFS devices send back to back NAC without waiting for new
44 * raised by UFS controller.
51 * If DL NAC error is seen multiple times with some vendor's UFS devices then
58 * Few Toshiba UFS device models advertise RX_MIN_ACTIVATETIME_CAPABILITY as
60 * from UFS device.
67 * It seems some UFS devices may keep drawing more than sleep current
68 * (atleast for 500us) from UFS rails (especially from VCCQ rail).
[all …]
|
| /kernel/linux/linux-6.6/fs/ufs/ |
| D | Kconfig | 3 tristate "UFS file system support (read only)"
8 OpenBSD and NeXTstep) use a file system called UFS. Some System V
12 experimental "UFS file system write support", below. Please read the
13 file <file:Documentation/admin-guide/ufs.rst> for more information.
27 To compile the UFS file system support as a module, choose M here: the
28 module will be called ufs.
33 bool "UFS file system write support (DANGEROUS)"
36 Say Y here if you want to try writing to UFS partitions. This is
37 experimental, so you should back up your UFS partitions beforehand.
40 bool "UFS debugging"
[all …]
|
| /kernel/linux/linux-5.10/fs/ufs/ |
| D | Kconfig | 3 tristate "UFS file system support (read only)"
7 OpenBSD and NeXTstep) use a file system called UFS. Some System V
11 experimental "UFS file system write support", below. Please read the
12 file <file:Documentation/admin-guide/ufs.rst> for more information.
26 To compile the UFS file system support as a module, choose M here: the
27 module will be called ufs.
32 bool "UFS file system write support (DANGEROUS)"
35 Say Y here if you want to try writing to UFS partitions. This is
36 experimental, so you should back up your UFS partitions beforehand.
39 bool "UFS debugging"
[all …]
|
| /kernel/linux/linux-6.6/drivers/ufs/ |
| D | Kconfig | 3 # UFS subsystem configuration
13 Enables support for UFS (Universal Flash Storage) host controllers.
14 A UFS host controller is an electronic component that is able to
15 communicate with a UFS card. UFS host controllers occur in
20 <file:Documentation/scsi/ufs.rst>.
22 (the one containing the directory /) is located on a UFS device.
26 source "drivers/ufs/core/Kconfig"
28 source "drivers/ufs/host/Kconfig"
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/phy/ |
| D | phy-mtk-ufs.txt | 1 MediaTek Universal Flash Storage (UFS) M-PHY binding
4 UFS M-PHY nodes are defined to describe on-chip UFS M-PHY hardware macro.
5 Each UFS M-PHY node should have its own node.
7 To bind UFS M-PHY with UFS host controller, the controller node should
8 contain a phandle reference to UFS M-PHY node.
10 Required properties for UFS M-PHY nodes:
12 "mediatek,mt8183-ufsphy" for ufs phy
14 - reg : Address and length of the UFS M-PHY register set.
|