Re: [PATCH v2] scsi: ufs: Configure clock in .hce_enable_notify() in Cadence UFS

2019-08-07 Thread Martin K. Petersen
Anil, > Configure CDNS_UFS_REG_HCLKDIV in .hce_enable_notify() instead of > .setup_clock() because if UFSHCD resets the controller ip because > of phy or device related errors then CDNS_UFS_REG_HCLKDIV is > reset to default value and .setup_clock() is not called later > in the sequence whereas

Re: [PATCH v2] scsi: ufs: Configure clock in .hce_enable_notify() in Cadence UFS

2019-08-05 Thread Vignesh Raghavendra
Hi, On 02/08/19 4:51 PM, Anil Varughese wrote: > Configure CDNS_UFS_REG_HCLKDIV in .hce_enable_notify() instead of > .setup_clock() because if UFSHCD resets the controller ip because > of phy or device related errors then CDNS_UFS_REG_HCLKDIV is > reset to default value and .setup_clock() is not

[PATCH v2] scsi: ufs: Configure clock in .hce_enable_notify() in Cadence UFS

2019-08-02 Thread Anil Varughese
Configure CDNS_UFS_REG_HCLKDIV in .hce_enable_notify() instead of .setup_clock() because if UFSHCD resets the controller ip because of phy or device related errors then CDNS_UFS_REG_HCLKDIV is reset to default value and .setup_clock() is not called later in the sequence whereas .hce_enable_notify