linux-kernel - Re: [PATCH v3 3/3] scsi: ufs: qcom: Call ufs_qcom_cfg

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <93ff21984da1fcc67a5d99e4f68fff00572cf59a.camel@gmail.com>
Date: Mon, 12 May 2025 10:58:33 +0200
From: Bean Huo <huobean@...il.com>
To: Ziqi Chen <quic_ziqichen@...cinc.com>, quic_cang@...cinc.com, 
 bvanassche@....org, mani@...nel.org, beanhuo@...ron.com,
 avri.altman@....com,  junwoo80.lee@...sung.com, martin.petersen@...cle.com,
 quic_nguyenb@...cinc.com,  quic_nitirawa@...cinc.com,
 quic_rampraka@...cinc.com, neil.armstrong@...aro.org, 
 luca.weiss@...rphone.com, konrad.dybcio@....qualcomm.com, 
 peter.wang@...iatek.com
Cc: linux-arm-msm@...r.kernel.org, linux-scsi@...r.kernel.org, Manivannan
	Sadhasivam <manivannan.sadhasivam@...aro.org>, "James E.J. Bottomley"
	 <James.Bottomley@...senPartnership.com>, open list
	 <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 3/3] scsi: ufs: qcom: Call ufs_qcom_cfg_timers() in
 clock scaling path

On Fri, 2025-05-09 at 15:50 +0800, Ziqi Chen wrote:
> From: Can Guo <quic_cang@...cinc.com>
> 
> ufs_qcom_cfg_timers() is clock freq dependent like ufs_qcom_set_core_clk_
> ctrl(), hence move ufs_qcom_cfg_timers() call to clock scaling path. In
> addition, do not assume the devfreq OPP freq is always the 'core_clock'
> freq although 'core_clock' is the first clock phandle in device tree, use
> ufs_qcom_opp_freq_to_clk_freq() to find the core clk freq.
> 
> Signed-off-by: Can Guo <quic_cang@...cinc.com>
> Co-developed-by: Ziqi Chen <quic_ziqichen@...cinc.com>
> Signed-off-by: Ziqi Chen <quic_ziqichen@...cinc.com>
> Tested-by: Luca Weiss <luca.weiss@...rphone.com>

Reviewed-by: Bean Huo <beanhuo@...ron.com>