Re: [PATCH 0/5] scsi: ufs: Fix device management timeouts and runtime PM errors
From: Bart Van Assche
Date: Mon Oct 26 2026 - 19:27:19 EST
On 10/24/26 6:34 PM, Stanley Jhu wrote:
Add ufshcd_rpm_resume_and_get() around pm_runtime_resume_and_get() and
convert the 20 external and helper call sites to abort and propagate the
error when resuming the W-LUN fails. The three lifecycle call sites in
ufshcd_rpm_dev_flush_recheck_work(), ufshcd_wl_shutdown(), and
ufshcd_remove(), plus ufshcd_err_handling_prepare(), are intentionally
left unchanged.
Patches 3/5 - 5/5 introduce a behavior change: a failed runtime suspend sets power.runtime_error but leaves the W-LUN in the RPM_ACTIVE state.
Today, sysfs, BSG and hwmon accesses still work in that state. With this series they all fail with -EINVAL until the error handler's
ufshcd_recover_pm_error() clears the flag. Is this behavior change
intentional?
Thanks,
Bart.