[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <015601d823d6$2c44f5c0$84cee140$@samsung.com>
Date: Thu, 17 Feb 2022 17:12:57 +0900
From: "Kiwoong Kim" <kwmad.kim@...sung.com>
To: "'Bean Huo'" <huobean@...il.com>,
"'Adrian Hunter'" <adrian.hunter@...el.com>,
"'Avri Altman'" <Avri.Altman@....com>,
<linux-scsi@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<alim.akhtar@...sung.com>, <jejb@...ux.ibm.com>,
<martin.petersen@...cle.com>, <beanhuo@...ron.com>,
<cang@...eaurora.org>, <sc.suh@...sung.com>,
<hy50.seo@...sung.com>, <sh425.lee@...sung.com>,
<bhoon95.kim@...sung.com>, <vkumar.1997@...sung.com>
Subject: RE: [PATCH v1] scsi: ufs: remove clk_scaling_lock when clkscaling
isn't supported.
> The name of clk_scaling_lock has explained everything, for the platform
> which doesn't support load-based clk scaling, doesn't need to hold this
> lock.
>
> Acked-by: Bean Huo <beanhuo@...ron.com>
Okay, thank you for your information.
I still have no idea of why the lock is required for ufshcd_exec_dev_cmd from the UFS specification w/o any featuring.
Powered by blists - more mailing lists