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_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
51 * - As soon as SW sees the DL NAC error, it should schedule the error handler
52 * - Error handler would sleep for 50ms to see if there are any fatal errors
53 * raised by UFS controller.
54 * - If there are fatal errors then SW does normal error recovery.
55 * - If there are no fatal errors then SW sends the NOP command to device
57 * - If NOP command times out, SW does normal error recovery
58 * - If NOP command succeed, skip the error handling.
60 * If DL NAC error is seen multiple times with some vendor's UFS devices then
64 #define UFS_DEVICE_QUIRK_RECOVERY_FROM_DL_NAC_ERRORS (1 << 2)
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).
78 * To avoid this situation, add 2ms delay before putting these UFS
84 * Some UFS devices require host PA_TACTIVATE to be lower than device
100 * Some UFS devices require VS_DebugSaveConfigTime is 0x10,
106 * Some pre-3.1 UFS devices can support extended features by upgrading
107 * the firmware. Enable this quirk to make UFS core driver probe and enable
113 * Some UFS devices require delay after VCC power rail is turned-off.
114 * Enable this quirk to introduce 5ms delays after VCC power-off during
120 * Some UFS devices require L2P entry should be swapped before being sent to the
121 * UFS device for HPB READ command.