scsi: ufs: Remove unused device quirks
The UFSHC driver defines a few quirks that are not used anywhere: UFS_DEVICE_QUIRK_BROKEN_LCC UFS_DEVICE_NO_VCCQ UFS_DEVICE_QUIRK_NO_LINK_OFF UFS_DEVICE_NO_FASTAUTO Let's remove them. Acked-by: Avri Altman <avri.altman@wdc.com> Acked-by: Alim Akhtar <alim.akhtar@samsung.com> Reviewed-by: Evan Green <evgreen@chromium.org> Signed-off-by: Marc Gonzalez <marc.w.gonzalez@free.fr> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
This commit is contained in:
parent
730679817d
commit
e9cb9655f8
@ -44,21 +44,6 @@ struct ufs_dev_fix {
|
||||
.quirk = (_quirk), \
|
||||
}
|
||||
|
||||
/*
|
||||
* If UFS device is having issue in processing LCC (Line Control
|
||||
* Command) coming from UFS host controller then enable this quirk.
|
||||
* When this quirk is enabled, host controller driver should disable
|
||||
* the LCC transmission on UFS host controller (by clearing
|
||||
* TX_LCC_ENABLE attribute of host to 0).
|
||||
*/
|
||||
#define UFS_DEVICE_QUIRK_BROKEN_LCC (1 << 0)
|
||||
|
||||
/*
|
||||
* Some UFS devices don't need VCCQ rail for device operations. Enabling this
|
||||
* quirk for such devices will make sure that VCCQ rail is not voted.
|
||||
*/
|
||||
#define UFS_DEVICE_NO_VCCQ (1 << 1)
|
||||
|
||||
/*
|
||||
* Some vendor's UFS device sends back to back NACs for the DL data frames
|
||||
* causing the host controller to raise the DFES error status. Sometimes
|
||||
@ -84,13 +69,6 @@ struct ufs_dev_fix {
|
||||
*/
|
||||
#define UFS_DEVICE_QUIRK_RECOVERY_FROM_DL_NAC_ERRORS (1 << 2)
|
||||
|
||||
/*
|
||||
* Some UFS devices may not work properly after resume if the link was kept
|
||||
* in off state during suspend. Enabling this quirk will not allow the
|
||||
* link to be kept in off state during suspend.
|
||||
*/
|
||||
#define UFS_DEVICE_QUIRK_NO_LINK_OFF (1 << 3)
|
||||
|
||||
/*
|
||||
* Few Toshiba UFS device models advertise RX_MIN_ACTIVATETIME_CAPABILITY as
|
||||
* 600us which may not be enough for reliable hibern8 exit hardware sequence
|
||||
@ -100,13 +78,6 @@ struct ufs_dev_fix {
|
||||
*/
|
||||
#define UFS_DEVICE_QUIRK_PA_TACTIVATE (1 << 4)
|
||||
|
||||
/*
|
||||
* Some UFS memory devices may have really low read/write throughput in
|
||||
* FAST AUTO mode, enable this quirk to make sure that FAST AUTO mode is
|
||||
* never enabled for such devices.
|
||||
*/
|
||||
#define UFS_DEVICE_NO_FASTAUTO (1 << 5)
|
||||
|
||||
/*
|
||||
* It seems some UFS devices may keep drawing more than sleep current
|
||||
* (atleast for 500us) from UFS rails (especially from VCCQ rail).
|
||||
|
@ -213,11 +213,8 @@ static struct ufs_dev_fix ufs_fixups[] = {
|
||||
/* UFS cards deviations table */
|
||||
UFS_FIX(UFS_VENDOR_SAMSUNG, UFS_ANY_MODEL,
|
||||
UFS_DEVICE_QUIRK_DELAY_BEFORE_LPM),
|
||||
UFS_FIX(UFS_VENDOR_SAMSUNG, UFS_ANY_MODEL, UFS_DEVICE_NO_VCCQ),
|
||||
UFS_FIX(UFS_VENDOR_SAMSUNG, UFS_ANY_MODEL,
|
||||
UFS_DEVICE_QUIRK_RECOVERY_FROM_DL_NAC_ERRORS),
|
||||
UFS_FIX(UFS_VENDOR_SAMSUNG, UFS_ANY_MODEL,
|
||||
UFS_DEVICE_NO_FASTAUTO),
|
||||
UFS_FIX(UFS_VENDOR_SAMSUNG, UFS_ANY_MODEL,
|
||||
UFS_DEVICE_QUIRK_HOST_PA_TACTIVATE),
|
||||
UFS_FIX(UFS_VENDOR_TOSHIBA, UFS_ANY_MODEL,
|
||||
@ -226,7 +223,6 @@ static struct ufs_dev_fix ufs_fixups[] = {
|
||||
UFS_DEVICE_QUIRK_PA_TACTIVATE),
|
||||
UFS_FIX(UFS_VENDOR_TOSHIBA, "THGLF2G9D8KBADG",
|
||||
UFS_DEVICE_QUIRK_PA_TACTIVATE),
|
||||
UFS_FIX(UFS_VENDOR_SKHYNIX, UFS_ANY_MODEL, UFS_DEVICE_NO_VCCQ),
|
||||
UFS_FIX(UFS_VENDOR_SKHYNIX, UFS_ANY_MODEL,
|
||||
UFS_DEVICE_QUIRK_HOST_PA_SAVECONFIGTIME),
|
||||
UFS_FIX(UFS_VENDOR_SKHYNIX, "hB8aL1" /*H28U62301AMR*/,
|
||||
|
Loading…
Reference in New Issue
Block a user