ufshcd_evaluate_tx_eqtr_fom(9)
π ufshcd_evaluate_tx_eqtr_fom(9) β like, the whole manual page, bestie
okay so this is a page straight out of the Kernel API Manual and it's called ufshcd_evaluate_tx_eqtr_fom(9), which lowkey sounds like a Wi-Fi password but it's actually a kernel function. stay with me, it's gonna slay β¨
πΈ NAME πΈ
ufshcd_evaluate_tx_eqtr_fom β literally just evaluates the TX EQTR FOM results. that's the whole vibe. no cap π
π¦ SYNOPSIS π¦
void ufshcd_evaluate_tx_eqtr_fom (struct ufs_hba *hba , struct
ufs_pa_layer_attr *pwr_mode , struct ufshcd_tx_eqtr_data *eqtr_data ,
struct tx_eqtr_iter *h_iter , struct tx_eqtr_iter *d_iter );
she returns void, she takes five arguments, she's booked and busy π
π ARGUMENTS π
hbaβ your per adapter instance, the main character of the whole situation πpwr_modeβ the target power mode, and yes she's carrying the gear and rate information in there, iykykeqtr_dataβ the TX EQTR data structure, the actual goods π¦h_iterβ the host TX EQTR iterator data structure, host side said "me first" π₯οΈd_iterβ the device TX EQTR iterator data structure, device side said "no me first" π±
β¨ DESCRIPTION β¨
so what she actually does: she evaluates the TX EQTR FOM results, then updates the host and device TX EQTR data accordingly β but only if the FOM have been improved compared to the previous iteration. like, she's not out here updating for no reason, she has standards πββοΈ then she records the TX EQTR FOM results. iconic behavior, honestly. record it, post it, periodt π₯
ngl the original spells it "accordingy" and honestly? we respect the typo. keeping the meaning, bestie: the update only happens when the FOM improved vs. the previous iteration. no fake glow-ups allowed π
π SEE ALSO π
like, go read the kernel file ./drivers/ufs/core/ufs-txeq.c first, and then the whole friend group of related functions β every single one, no skipping π«Ά
ufshcd_configure_precoding(9)ufshcd_apply_tx_eq_settings(9)ufshcd_get_rx_fom(9)tx_eqtr_iter_try_update(9)tx_eqtr_iter_update(9)ufshcd_tx_eqtr_iter_init(9)adapt_cap_to_t_adapt(9)adapt_cap_to_t_adapt_l0l3(9)adapt_cap_to_t_adapt_l0l1l2l3(9)ufshcd_setup_tx_eqtr_adapt_length(9)ufshcd_compose_tx_eqtr_setting(9)ufshcd_apply_tx_eqtr_settings(9)ufshcd_update_tx_eq_params(9)__ufshcd_tx_eqtr(9)ufshcd_tx_eqtr_prepare(9)ufshcd_tx_eqtr(9)ufshcd_config_tx_eq_settings(9)ufshcd_apply_valid_tx_eq_settings(9)ufshcd_retrain_tx_eq(9)ufshcd_extract_tx_eq_settings_attrs(9)ufshcd_update_tx_eq_settings_attrs(9)
okay that's the whole page, you ate that π
β¨ this little gem lives in ./drivers/ufs/core, it's dated October 2026, and yes the header up top and the footer down here are both just ufshcd_evaluate_tx_eqtr_fom(9) again β she's consistent, she's committed, she's giving main character energy πππ
π¦ 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