ath5k_combi...pcdac_curves(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ath5k_combine_linear_pcdac_curves β€” Kernel API Manual ✨

okay so bestie, you found the page for ath5k_combine_linear_pcdac_curves in the Kernel API Manual, and honestly? we're about to get into some PHY table-combining lore πŸ¦‹


🌸 NAME 🌸

ath5k_combine_linear_pcdac_curves β€” combine the available PCDAC Curves, that's the whole gig πŸ’–


✨ SYNOPSIS ✨

void ath5k_combine_linear_pcdac_curves (struct ath5k_hw *ah , s16*
       table_min , s16 *table_max , u8 pdcurves );

literally just four args, no cap πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • ah β€” The struct ath5k_hw itself, the main character of this whole situation πŸ’…
  • table_min β€” Minimum power (x min), the low end of the vibe check πŸ“‰
  • table_max β€” Maximum power (x max), the high end, she's giving range 🌈
  • pdcurves β€” Number of pd curves, so like, the count πŸ“

πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the tea: this function combines the available XPD Curves and fills the Linear Power to PCDAC table on RF5112. And RFX112 can have up to 2 curves β€” one for the low txpower range and one for the higher txpower range. Two icons, one table πŸ’–

We need to put them both on pcdac_out and place them in the correct location. Slay, positioning matters.

But wait β€” in case we only have one curve available, we just fit it on pcdac_out. And no, that's not a downgrade, it's supposed to cover the entire range of available pwr levels since it's always the higher power curve. She's versatile like that 😌

And if needed? We extrapolate below and above the final table. Extrapolation is giving main character energy fr fr πŸ”₯


πŸ‘‘ SEE ALSO πŸ‘‘

okay this list is long bestie, buckle up, every single one is here:


and that's the whole page bestie, no gatekeeping 🫢 this one lives in ./drivers/net/wireless/ath/ath5k β€” the Kernel API Manual, dated October 2026, filed under ath5k_combi...pcdac_curves(9). ily, go combine some curves πŸ’œβœ¨

πŸ“¦ where this page comes from