ufshcd_update_tx_eq_params(9)

📦 version 7.3.1, in nixpkgs unstable

💖 ufshcd_update_tx_eq_params(9) 💖

okay so this is a page straight out of the Kernel API Manual, bestie — it's the glow-up guide for ufshcd_update_tx_eq_params, and honestly? she's lowkey the main character of TX Equalization bookkeeping. let's get into it 🎀

✨ NAME ✨

ufshcd_update_tx_eq_params — Update TX Equalization params 🌸

✨ SYNOPSIS ✨

void ufshcd_update_tx_eq_params (struct ufshcd_tx_eq_params *params ,
struct ufs_pa_layer_attr *pwr_mode , struct ufshcd_tx_eqtr_data
*eqtr_data );

like, three pointers walk into a function. no return value. void. she just does the thing and leaves 💅

✨ ARGUMENTS ✨

  • params — the TX EQ parameters data structure 🫶 this is where the good stuff lives
  • pwr_mode — the target power mode, and yes she's carrying both the gear and the rate, iconic
  • eqtr_data — the TX EQTR data structure, aka the receipts 📋

✨ DESCRIPTION ✨

so the whole vibe here: you update the TX Equalization params using the results that came out of the TX EQTR data. that's the assignment, and she ate 🔥

also — and this is the part you cannot skip — check the TX EQTR FOM value for every single TX lane inside the TX EQTR data. every one. no cherry-picking.

and if a TX lane got a FOM value of 0? 😭 that lane is not okay. so you restore the TX Equalization settings from the last known valid TX Equalization params — and specifically for that specific TX lane, not the whole squad. per-lane rescue mission, periodt 👑

ngl, don't sleep on the FOM 0 check. that's the whole safety net 🧚

✨ SEE ALSO ✨

kernel file ./drivers/ufs/core/ufs-txeq.c 💜 plus the entire friend group:

like, that's a whole group chat right there 💀

and that's the page bestie!! 🦋 this little number lives in ./drivers/ufs/core, dated October 2026, and it's literally titled ufshcd_update_tx_eq_params(9). go forth and equalize ✨💖🎀

📦 where this page comes from