ufs_qcom_fw_...device_reset(9)

✨ NAME ✨

ufs_qcom_fw_managed_device_reset — reset that UFS device when it's living that FW-managed life 💅

so like, quick intro bestie: this page is from the Kernel API Manual, and it's all about ufs_qcom_fw_managed_device_reset. yeah, the name is a whole mouthful, i know 😭

🦋 SYNOPSIS 🦋

int ufs_qcom_fw_managed_device_reset (struct ufs_hba *hba );

🎀 ARGUMENTS 🎀

• hba — pointer to UFS host bus adapter. that's it, that's the whole argument list, she's low maintenance 💖

🌸 DESCRIPTION 🌸

okay so picture this: in the firmware-managed reset model, the power domain gets powered on by genpd before the UFS controller driver even probes. main character genpd did it first, no notes 👑

but for the resets that come after that — think suspend/resume situations, or recovery — the UFS driver can't just sit there looking cute. nope. it must explicitly invoke PM runtime. no cap, that's on the driver, every time, fr fr 🔥

⭐ RETURN ⭐

• 0 on success 🎉
• a negative error code on failure 😭

💜 SEE ALSO 💜

• Kernel file ./drivers/ufs/host/ufs-qcom.c — go read the source bestie, iykyk
• ufs_qcom_config_ice_allocator(9)
• ufs_qcom_cfg_timers(9)
• ufs_qcom_double_t_adapt_l0l1l2l3(9)
• ufs_qcom_advertise_quirks(9)
• ufs_qcom_setup_clocks(9)
• ufs_qcom_init(9)
• ufs_qcom_set_clk_40ns_cycles(9)
• ufs_qcom_device_reset(9)
• ufs_qcom_probe(9)
• ufs_qcom_remove(9)

okay that's the whole page, you ate that 🫶 it lives over in ./drivers/ufs/host, dated October 2026, and it's filed under ufs_qcom_fw_...device_reset(9) in case you need to find her again. periodt 💅✨