summaryrefslogtreecommitdiff
path: root/scripts/stackusage
diff options
context:
space:
mode:
authorManivannan Sadhasivam <manivannan.sadhasivam@linaro.org>2025-02-19 16:20:47 +0530
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-03-07 18:25:28 +0100
commit465a8143238b5339391919fbf553aa27395bea08 (patch)
tree123d0125f2abbe90824f95f5244370f34ef54ece /scripts/stackusage
parentb5038504da33f58768dfdd3cfe956299f3d87ff1 (diff)
downloadlinux-465a8143238b5339391919fbf553aa27395bea08.tar.gz
linux-465a8143238b5339391919fbf553aa27395bea08.tar.bz2
linux-465a8143238b5339391919fbf553aa27395bea08.zip
scsi: ufs: core: Set default runtime/system PM levels before ufshcd_hba_init()
[ Upstream commit fe06b7c07f3fbcce2a2ca6f7b0d543b5699ea00f ] 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 <quic_nguyenb@quicinc.com> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> Link: https://lore.kernel.org/r/20250219105047.49932-1-manivannan.sadhasivam@linaro.org Reviewed-by: Bart Van Assche <bvanassche@acm.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts/stackusage')
0 files changed, 0 insertions, 0 deletions