lkml.org 
[lkml]   [2022]   [Jan]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: [PATCH v2] scsi: ufs: modify Tactive time setting conditions
Date
> The Tactive time determine the waiting time before burst
> at hibern8 exit and is determined by H/W at linkup state
> However, in the case of samsung devices, guided host's Tactive time
> +100us for stability.
> If the HCI's Tactive time is equal or greater than the device,
> +100us should be set.
This way you are changing this for everyone - not just for Samsung.
e.g. Qualcomm are using this quirk as well for WDC devices.

Thanks,
Avri

>
> Signed-off-by: SEO HOYOUNG <hy50.seo@samsung.com>
> ---
> drivers/scsi/ufs/ufshcd.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
> index 1049e41abd5b..460d2b440d2e 100644
> --- a/drivers/scsi/ufs/ufshcd.c
> +++ b/drivers/scsi/ufs/ufshcd.c
> @@ -7815,7 +7815,7 @@ static int ufshcd_quirk_tune_host_pa_tactivate(struct
> ufs_hba *hba)
> peer_pa_tactivate_us = peer_pa_tactivate *
> gran_to_us_table[peer_granularity - 1];
>
> - if (pa_tactivate_us > peer_pa_tactivate_us) {
> + if (pa_tactivate_us >= peer_pa_tactivate_us) {
> u32 new_peer_pa_tactivate;
>
> new_peer_pa_tactivate = pa_tactivate_us /
> --
> 2.26.0

\
 
 \ /
  Last update: 2022-01-07 11:57    [W:0.074 / U:0.080 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site