ufshcd_extr...ttings_attrs(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ufshcd_extract_tx_eq_settings_attrs(9) β€” like, the actual page

okay so this is from the Kernel API Manual bestie, and it's a kernel function page, so buckle up πŸŽ€


✨ NAME ✨

ufshcd_extract_tx_eq_settings_attrs β€” my girl pulls the TX Equalization settings out of the UFS attributes, no cap πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

void ufshcd_extract_tx_eq_settings_attrs (struct ufs_hba *hba , u8 gear );

🌸 ARGUMENTS 🌸

  • hba β€” the per adapter instance, aka your main character struct 🫢
  • gear β€” the target gear 🌈

πŸ‘‘ DESCRIPTION πŸ‘‘

Okay so picture this: we already did an EQTR procedure at some point, right, and it figured out the optimal TX Equalization parameters β€” PreShoot, DeEmphasis, and the PreCoding enable. Those little guys got stashed away in the UFS attributes, and this function is the one that goes and gets them back out. πŸ’…

The function reads:

  1. qTxEQGnSettings (64-bit): the main attribute, containing the PreShoot and DeEmphasis values for both host and device TX lanes πŸ”₯
  2. wTxEQGnSettingsExt (16-bit): the extended attribute, containing the PreCoding enable flags and a validity indicator ⭐

literally just goes in, grabs both, done. iconic behavior tbh ✨


🧚 SEE ALSO 🧚

Kernel file ./drivers/ufs/core/ufs-txeq.c β€” and bestie, the whole friend group:


bestie reminder: this is the extract function. it reads the stored settings, it does not apply them. go read ufshcd_apply_tx_eq_settings(9) if that's what you're after, iykyk πŸ’€

mwah πŸ’œ that's the whole page!! this came out of ./drivers/ufs/core, dated October 2026, under the Kernel API Manual banner β€” go off, ufs-txeq.c, you ate πŸ“βœ¨

πŸ“¦ where this page comes from