STRUCT UFSHCD_TX_EQ_PARAMS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ struct ufshcd_tx_eq_params β€” Kernel API Manual ✨

okay so bestie, this is struct ufshcd_tx_eq_params and it's literally the TX Equalization parameters structure πŸ’… it's giving "let me hold all the vibe info about TX EQ" and honestly? iconic.


πŸŽ€ NAME πŸŽ€

struct ufshcd_tx_eq_params β€” the TX Equalization parameters structure, no cap πŸ¦‹


🌸 SYNOPSIS 🌸

struct ufshcd_tx_eq_params {
    struct ufshcd_tx_eq_settings host[UFS_MAX_LANES];
    struct ufshcd_tx_eq_settings device[UFS_MAX_LANES];
    struct ufshcd_tx_eqtr_record *eqtr_record;
    bool is_valid;
    bool is_applied;
    bool is_trained;
    bool from_dt;
 };

πŸ’– Members πŸ’–

  • host β€” the TX EQ settings for the host TX Lanes 🫢 like, the home team's settings, periodt.
  • device β€” the TX EQ settings for the device TX Lanes ✨ the other side's settings, matching energy.
  • eqtr_record β€” pointer to the TX EQTR record πŸ“‹ it's just pointing at the record, that's the whole job.
  • is_valid β€” True if the parameter contains valid TX Equalization settings βœ… the vibe check flag, fr fr.
  • is_applied β€” True if settings have been applied to UniPro of both sides πŸ’« both sides!! applied!! we love to see it.
  • is_trained β€” True if parameters were obtained from the TX EQTR procedure 🧚 trained up and ready, iykyk.
  • from_dt β€” True if settings are from Device Tree 🌳 device tree origin story, lowkey cute.

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./include/ufs/ufshcd.h, plus all these besties: struct uic_command(9), struct ufshcd_lrb(9), struct ufs_query_req(9), struct ufs_query_res(9), struct ufs_query(9), struct ufs_dev_cmd(9), struct ufs_clk_info(9), struct tx_eqtr_iter(9), struct ufshcd_tx_eq_settings(9), struct ufshcd_tx_eqtr_data(9), struct ufshcd_tx_eqtr_record(9), struct ufs_hba_variant_ops(9), struct ufs_clk_gating(9), struct ufs_clk_scaling(9), struct ufs_event_hist(9), struct ufs_stats(9), enum ufshcd_state(9), enum ufshcd_pmc_policy(9), struct ufshcd_mcq_opr_info_t(9), struct ufs_hba(9), struct ufs_hw_queue(9), ufshcd_rmwl(9), ufshcd_set_variant(9), ufshcd_get_variant(9) πŸ’€ that's a whole friend group and every single one of them made the list.


alright bestie, that's the whole page πŸŽ€ it lives in ./include/ufs, dated October 2026, from the Kernel API Manual β€” mwah, slay, go read some source code πŸ’œπŸŒˆ

πŸ“¦ where this page comes from