ufs_qcom_setup_clocks(9)
β¨ ufs_qcom_setup_clocks(9) β¨
okay so bestie, this is a page from the Kernel API Manual, and it's all about one lil' function that turns clocks on and off π°οΈπ
πΈ NAME πΈ
ufs_qcom_setup_clocks β enables/disable clocks
π SYNOPSIS π
int ufs_qcom_setup_clocks (struct ufs_hba *hba , bool on , enum
ufs_notify_change_status status );
π¦ ARGUMENTS π¦
hbaβ the host controller instance, aka the main character here πonβ if it'strue, we enable the clocks; otherwise we disable them. Simple as that, no cap πstatusβ eitherPRE_CHANGEorPOST_CHANGEnotify. pick your moment bestie β°
π DESCRIPTION π
So here's the tea β: there are certain clocks that come from the PHY, which means they gotta be managed together with the controller clocks β and lowkey that's also just better for power saving, fr fr π±β¨
That's literally why the phy_power_off/on calls live inside ufs_qcom_setup_clocks β so that the PHY's regulators & clks can be turned on/off right along with UFS's clocks. team work makes the dream work π«Ά
π₯ RETURN π₯
0 on success, non-zero on failure. slay when it works, sad girl hours when it doesn't π
π SEE ALSO π
Kernel file ./drivers/ufs/host/ufs-qcom.c
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_init(9)ufs_qcom_set_clk_40ns_cycles(9)ufs_qcom_device_reset(9)ufs_qcom_fw_managed_device_reset(9)ufs_qcom_probe(9)ufs_qcom_remove(9)
π and that's the whole page bestie! it lives in ./drivers/ufs/host, it's dated October 2026, and that's the ufs_qcom_setup_clocks(9) moment β periodt πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms