| /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 …]
|
| D | ufs-exynos.h | 3 * UFS Host Controller driver for Exynos specific extensions
85 #define UNIPRO_PCLK_PERIOD(ufs) (NSEC_PER_SEC / ufs->pclk_rate) argument
163 int (*drv_init)(struct device *dev, struct exynos_ufs *ufs);
164 int (*pre_link)(struct exynos_ufs *ufs);
165 int (*post_link)(struct exynos_ufs *ufs);
166 int (*pre_pwr_change)(struct exynos_ufs *ufs,
168 int (*post_pwr_change)(struct exynos_ufs *ufs,
217 #define for_each_ufs_rx_lane(ufs, i) \ argument
218 for (i = (ufs)->rx_sel_idx; \
219 i < (ufs)->rx_sel_idx + (ufs)->avail_ln_rx; i++)
[all …]
|
| /kernel/linux/linux-4.19/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.
26 Description: This file shows the device class. This is one of the UFS
28 the descriptor could be found at UFS specifications 2.1.
34 Description: This file shows the UFS storage subclass. This is one of
35 the UFS device descriptor parameters. The full information
36 about the descriptor could be found at UFS specifications 2.1.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/scsi/ |
| D | ufs.txt | 9 2. UFS Architecture Overview
11 2.2 UFS Transport Protocol(UTP) layer
12 2.3 UFS Interconnect(UIC) Layer
14 3.1 UFS controller initialization
16 3.3 UFS error handling
23 Universal Flash Storage(UFS) is a storage specification for flash devices.
27 is defined by JEDEC Solid State Technology Association. UFS is based
28 on MIPI M-PHY physical layer standard. UFS uses MIPI M-PHY as the
31 The main goals of UFS is to provide,
33 For UFS version 1.0 and 1.1 the target performance is as follows,
[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-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 …]
|
| D | cdns,ufshc.txt | 1 * Cadence Universal Flash Storage (UFS) Controller
3 UFS nodes are defined to describe on-chip UFS host controllers.
4 Each UFS controller instance should have its own node.
10 "cdns,ufshc-m31-16nm" - CDNS UFS HC + M31 16nm PHY
12 "jedec,ufs-2.0"
14 - reg : Address and length of the UFS register set.
25 ufs@fd030000 {
26 compatible = "cdns,ufshc", "jedec,ufs-2.0";
|
| D | tc-dwc-g210-pltfrm.txt | 1 * Universal Flash Storage (UFS) DesignWare Host Controller
3 DWC_UFS nodes are defined to describe on-chip UFS host controllers and MPHY.
4 Each UFS controller instance should have its own node.
13 "jedec,ufs-1.1"
14 "jedec,ufs-2.0"
17 - interrupts : <interrupt mapping for UFS host controller IRQ>
20 dwc-ufs@d0000000 {
23 "jedec,ufs-2.0";
|
| /kernel/linux/linux-4.19/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 - reg : should contain UFS register address space & UFS SYS CTRL register address,
22 - reset-names : reset node register, the "rst" corresponds to reset the whole UFS IP.
26 ufs: ufs@ff3b0000 {
27 compatible = "hisilicon,hi3660-ufs", "jedec,ufs-1.1";
29 /* 1: UFS SYS CTRL */
|
| 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
36 compatible = "qcom,ufs-phy-qmp-20nm";
|
| 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", may
12 - interrupts : <interrupt mapping for UFS host controller IRQ>
16 - phys : phandle to UFS PHY node
18 with "phys" attribute, provides phandle to UFS PHY node
19 - vdd-hba-supply : phandle to UFS host controller supply regulator node
23 - vcc-supply-1p8 : For embedded UFS devices, valid VCC range is 1.7-1.95V
26 UFS cards this property is invalid and valid VCC range is
[all …]
|
| D | tc-dwc-g210-pltfrm.txt | 1 * Universal Flash Storage (UFS) DesignWare Host Controller
3 DWC_UFS nodes are defined to describe on-chip UFS host controllers and MPHY.
4 Each UFS controller instance should have its own node.
13 "jedec,ufs-1.1"
14 "jedec,ufs-2.0"
17 - interrupts : <interrupt mapping for UFS host controller IRQ>
20 dwc-ufs@d0000000 {
23 "jedec,ufs-2.0";
|
| /kernel/linux/linux-4.19/drivers/scsi/ufs/ |
| 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.txt>.
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 | 30 * ufs_dev_fix - ufs device quirk info
31 * @card: ufs card details
49 * If UFS device is having issue in processing LCC (Line Control
50 * Command) coming from UFS host controller then enable this quirk.
52 * the LCC transmission on UFS host controller (by clearing
58 * Some UFS devices don't need VCCQ rail for device operations. Enabling this
64 * Some vendor's UFS device sends back to back NACs for the DL data frames
66 * such UFS devices send back to back NAC without waiting for new
75 * raised by UFS controller.
82 * If DL NAC error is seen multiple times with some vendor's UFS devices then
[all …]
|
| /kernel/linux/linux-4.19/fs/ufs/ |
| D | Kconfig | 2 tristate "UFS file system support (read only)"
6 OpenBSD and NeXTstep) use a file system called UFS. Some System V
10 experimental "UFS file system write support", below. Please read the
11 file <file:Documentation/filesystems/ufs.txt> for more information.
25 To compile the UFS file system support as a module, choose M here: the
26 module will be called ufs.
31 bool "UFS file system write support (DANGEROUS)"
34 Say Y here if you want to try writing to UFS partitions. This is
35 experimental, so you should back up your UFS partitions beforehand.
38 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-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.
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | ufs.rst | 2 Using UFS
5 mount -t ufs -o ufstype=type_of_ufs device dir
8 UFS Options
12 UFS is a file system widely used in different operating systems.
15 type of ufs automatically. That's why user must specify type of
16 ufs manually by mount option ufstype. Possible values are:
19 old format of ufs
67 Any ufs bug report you can send to daniel.pirkl@email.cz or
|