[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MN2PR04MB699133D84C627AE30C6A50CDFCDF0@MN2PR04MB6991.namprd04.prod.outlook.com>
Date: Wed, 31 Jul 2019 10:09:54 +0000
From: Avri Altman <Avri.Altman@....com>
To: Anil Varughese <aniljoy@...ence.com>,
"alim.akhtar@...sung.com" <alim.akhtar@...sung.com>,
"pedrom.sousa@...opsys.com" <pedrom.sousa@...opsys.com>
CC: "jejb@...ux.ibm.com" <jejb@...ux.ibm.com>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
"hare@...e.de" <hare@...e.de>,
"rafalc@...ence.com" <rafalc@...ence.com>,
"mparab@...ence.com" <mparab@...ence.com>,
"jank@...ence.com" <jank@...ence.com>,
"vigneshr@...com" <vigneshr@...com>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] scsi: ufs: Additional clock initialization in Cadence UFS
>
> Configure CDNS_UFS_REG_HCLKDIV in .hce_enable_notify()
> 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
> will be called everytime controller is reenabled.
>
> Signed-off-by: Anil Varughese <aniljoy@...ence.com>
Reviewed-by: Avri Altman <avri.altman@....com>
Powered by blists - more mailing lists