aboutsummaryrefslogtreecommitdiffstats
path: root/net/unix/af_unix.c
diff options
context:
space:
mode:
authorManivannan Sadhasivam <[email protected]>2025-02-19 10:50:47 +0000
committerMartin K. Petersen <[email protected]>2025-02-21 02:29:21 +0000
commitfe06b7c07f3fbcce2a2ca6f7b0d543b5699ea00f (patch)
tree19c24d773db72da6d08e93a24afe79d2b0e0d59a /net/unix/af_unix.c
parentscsi: core: Clear driver private data when retrying request (diff)
downloadkernel-fe06b7c07f3fbcce2a2ca6f7b0d543b5699ea00f.tar.gz
kernel-fe06b7c07f3fbcce2a2ca6f7b0d543b5699ea00f.zip
scsi: ufs: core: Set default runtime/system PM levels before ufshcd_hba_init()
Commit bb9850704c04 ("scsi: ufs: core: Honor runtime/system PM levels if set by host controller drivers") introduced the check for setting default PM levels only if the levels are uninitialized by the host controller drivers. But it missed the fact that the levels could be initialized to 0 (UFS_PM_LVL_0) on purpose by the controller drivers. Even though none of the drivers are doing so now, the logic should be fixed irrespectively. So set the default levels unconditionally before calling ufshcd_hba_init() API which initializes the controller drivers. It ensures that the controller drivers could override the default levels if required. Fixes: bb9850704c04 ("scsi: ufs: core: Honor runtime/system PM levels if set by host controller drivers") Reported-by: Bao D. Nguyen <[email protected]> Signed-off-by: Manivannan Sadhasivam <[email protected]> Link: https://lore.kernel.org/r/[email protected] Reviewed-by: Bart Van Assche <[email protected]> Signed-off-by: Martin K. Petersen <[email protected]>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions