linux-kernel - Re: [PATCH v4 6/8] scsi: ufs: core: Check if scaling up is required when disable clkscale

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 for Android: free password hash cracker in your pocket

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

Message-ID: <989a98d1aa0d76c1e646222d8c9a8440dcd2d325.camel@gmail.com>
Date: Mon, 10 Feb 2025 19:17:22 +0100
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
Cc: linux-arm-msm@...r.kernel.org, linux-scsi@...r.kernel.org, Neil
 Armstrong <neil.armstrong@...aro.org>, Alim Akhtar
 <alim.akhtar@...sung.com>, "James E.J. Bottomley"
 <James.Bottomley@...senPartnership.com>, Peter Wang
 <peter.wang@...iatek.com>, Manivannan Sadhasivam
 <manivannan.sadhasivam@...aro.org>, Andrew Halaney <ahalaney@...hat.com>,
 open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 6/8] scsi: ufs: core: Check if scaling up is required
 when disable clkscale

On Mon, 2025-02-10 at 18:02 +0800, Ziqi Chen wrote:
> When disabling clkscale via the clkscale_enable sysfs entry, UFS
> driver
> shall perform scaling up once regardless. Check if scaling up is
> required
> or not first to avoid repetitive work.
> 
> Co-developed-by: Can Guo <quic_cang@...cinc.com>
> Signed-off-by: Can Guo <quic_cang@...cinc.com>
> Signed-off-by: Ziqi Chen <quic_ziqichen@...cinc.com>
> Reviewed-by: Bart Van Assche <bvanassche@....org>
> Tested-by: Neil Armstrong <neil.armstrong@...aro.org>

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