ufshcd_appl...qtr_settings(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ufshcd_appl...qtr_settings(9) πŸ’…

okay bestie, welcome to the Kernel API Manual entry for ufshcd_apply_tx_eqtr_settings β€” yes, the header is out here doing its little ufshcd_appl...qtr_settings(9) abbreviation moment, and we're still gonna understand it fr fr 🫢✨


🌸 NAME 🌸

ufshcd_apply_tx_eqtr_settings β€” Apply TX EQTR setting πŸŽ€

That's the whole name vibe: this function applies TX EQTR setting, no cap.


✨ SYNOPSIS ✨

the signature is literally giving:

int ufshcd_apply_tx_eqtr_settings (struct ufs_hba *hba , struct
       ufs_pa_layer_attr *pwr_mode , struct tx_eqtr_iter *h_iter , struct
       tx_eqtr_iter *d_iter );

πŸŽ€ ARGUMENTS πŸŽ€

  • hba β€” per adapter instance 🫢
  • pwr_mode β€” target power mode containing gear and rate information 🌈
  • h_iter β€” host TX EQTR iterator data structure πŸ‘‘
  • d_iter β€” device TX EQTR iterator data structure πŸ¦‹

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so the return tea is literally: Returns 0 on success, negative error code otherwise πŸ˜­πŸ’–

That's the description, bestie β€” no secret bonus lore, iykyk.


πŸ’– SEE ALSO πŸ’–

kernel file ./drivers/ufs/core/ufs-txeq.c is right there in the mix, and the see-also besties are:


πŸ’œ cute little sign-off time: source/version ./drivers/ufs/core, date October 2026, and this page is ufshcd_appl...qtr_settings(9) β€” periodt, bestie πŸ«ΆπŸŽ€βœ¨

πŸ“¦ where this page comes from