ufshcd_negotiate_pwr_params(9)
π ufshcd_negotiate_pwr_params(9) π
okay bestie, welcome to the Kernel API Manual π β yes that's the manual name, we're fancy here. Today's main character is ufshcd_negotiate_pwr_params, a lil function with a big job. Let's get into it β¨
πΈ NAME πΈ
ufshcd_negotiate_pwr_params β literally its whole thing is finding power mode settings that are supported by both the controller and the device π«Ά like a group chat where everybody has to agree on the plan or nobody's going anywhere.
β¨ SYNOPSIS β¨
int ufshcd_negotiate_pwr_params (const struct ufs_host_params
*host_params , const struct ufs_pa_layer_attr *dev_max , struct
ufs_pa_layer_attr *agreed_pwr );
that's the whole signature, no cap π
π¦ ARGUMENTS π¦
host_paramsβ pointer to host parameters π (the host's side of the story)dev_maxβ pointer to device attributes π (the device's side of the story)agreed_pwrβ returned agreed attributes π€ (where the compromise gets written down β this is the main character of the output, honestly)
β RETURN β
0 on success π β and a non-zero value on failure π no middle ground, it's giving pass/fail semester.
π SEE ALSO π
Kernel file ./drivers/ufs/host/ufshcd-pltfrm.c
and the whole friend group, fr fr:
ufshcd_parse_regulator_info(9)ufshcd_parse_tx_eq_settings_for_gear(9)ufshcd_parse_clock_min_max_freq(9)ufshcd_parse_gear_limits(9)ufshcd_pltfrm_init(9)ufshcd_pltfrm_remove(9)
π§ tiny reminder: this page lives in./drivers/ufs/host, dated October 2026, and it's pageufshcd_negotiate_pwr_params(9)of the Kernel API Manual β so if you're citing it, cite it cute π
k bye bestie, go negotiate those power params, slay ππ₯π
π¦ 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