ufshcd_compo...eqtr_setting(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

okay bestie, welcome to the ufshcd_compo...eqtr_setting(9) page from the Kernel API Manual β€” and yes, that clipped-looking name with the ... is exactly the name, so we are keeping it, periodt. πŸ’… The function here is ufshcd_compose_tx_eqtr_setting, and its whole gig is: compose TX EQTR setting. That's the name, that's the vibe, no cap. ✨

✨ SYNOPSIS ✨

here's the signature, character for character, bestie:

u32 ufshcd_compose_tx_eqtr_setting (struct tx_eqtr_iter *iter , int
       num_lanes );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • iter β€” TX EQTR iterator data structure. it's the iterator data structure doing iterator things, iykyk. 🫢
  • num_lanes β€” number of active lanes. literally how many lanes are active. πŸ›£οΈ

🌈 DESCRIPTION 🌈

Returns composed TX EQTR setting, and the same setting is used for all active lanes. so yeah: one composed TX EQTR setting, all active lanes, that's the whole story. iconic behavior, honestly. πŸ‘‘πŸ”₯

πŸ’– SEE ALSO πŸ’–

Kernel file: ./drivers/ufs/core/ufs-txeq.c β€” go look, bestie. πŸ“‚βœ¨


okay that's the whole page, mwah πŸ’‹ β€” the source/version spot is ./drivers/ufs/core, the date is October 2026, and the page is ufshcd_compo...eqtr_setting(9). bye bestie, go compose those TX EQTR settings and slay. πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from