Lines Matching +full:ufs +full:- +full:2

1 /* SPDX-License-Identifier: GPL-2.0-only */
3  * Copyright (c) 2014-2016, The Linux Foundation. All rights reserved.
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
42  * - As soon as SW sees the DL NAC error, it should schedule the error handler
43  * - Error handler would sleep for 50ms to see if there are any fatal errors
44  *   raised by UFS controller.
45  *    - If there are fatal errors then SW does normal error recovery.
46  *    - If there are no fatal errors then SW sends the NOP command to device
48  *        - If NOP command times out, SW does normal error recovery
49  *        - If NOP command succeed, skip the error handling.
51  * If DL NAC error is seen multiple times with some vendor's UFS devices then
55 #define UFS_DEVICE_QUIRK_RECOVERY_FROM_DL_NAC_ERRORS (1 << 2)
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).
69  * To avoid this situation, add 2ms delay before putting these UFS
75  * Some UFS devices require host PA_TACTIVATE to be lower than device
91  * Some UFS devices require VS_DebugSaveConfigTime is 0x10,
97  * Some pre-3.1 UFS devices can support extended features by upgrading
98  * the firmware. Enable this quirk to make UFS core driver probe and enable
104  * Some UFS devices require delay after VCC power rail is turned-off.
105  * Enable this quirk to introduce 5ms delays after VCC power-off during