ath5k_get_c...unding_piers(9)
β¨ NAME β¨
ath5k_get_chan_pcal_surrounding_piers β get surrounding calibration piers for a given channel. π
okay bestie, this is the Kernel API Manual page for ath5k_get_chan_pcal_surrounding_piers β the tiny header version gets chopped into ath5k_get_c...unding_piers(9), which is giving βmy name got ate by the terminalβ energy, but the full function name is right there and weβre obsessed. β¨
πΈ SYNOPSIS πΈ
void ath5k_get_chan_pcal_surrounding_piers (struct ath5k_hw *ah , struct ieee80211_channel *channel , struct ath5k_chan_pcal_info **pcinfo_l , struct ath5k_chan_pcal_info **pcinfo_r );
π ARGUMENTS π
ahβ thestruct ath5k_hw. thatβs the hardware bestie in question π«Άchannelβ thestruct ieee80211_channel. the channel weβre doing all this for πpcinfo_lβ thestruct ath5k_chan_pcal_infoto put the left cal. pier. left pier goes here, no cap πΈpcinfo_rβ thestruct ath5k_chan_pcal_infoto put the right cal. pier. right pier goes here, periodt π
π¦ DESCRIPTION π¦
okay so the whole slay here is: get the surrounding per-channel power calibration piers for a given frequency so that we can interpolate between them and come up with an appropriate dataset for our current channel. literally thatβs the vibe check. π«
we grab the calibration piers on either side, interpolate between them, and end up with the right dataset for the channel we actually care about. iconic behavior honestly. π
π SEE ALSO π
- Kernel file
./drivers/net/wireless/ath/ath5k/phy.cβ PHY related functions(9) ath5k_hw_radio_revision(9)ath5k_channel_ok(9)ath5k_hw_chan_has_spur_noise(9)ath5k_hw_rfb_op(9)ath5k_hw_write_ofdm_timings(9)ath5k_hw_phy_disable(9)ath5k_hw_wait_for_synth(9)- RF Gain optimization(9)
ath5k_hw_rfgain_opt_init(9)ath5k_hw_request_rfgain_probe(9)ath5k_hw_rf_gainf_corr(9)ath5k_hw_rf_check_gainf_readback(9)ath5k_hw_rf_gainf_adjust(9)ath5k_hw_gainf_calibrate(9)ath5k_hw_rfgain_init(9)ath5k_hw_rfregs_init(9)ath5k_hw_rf5110_chan2athchan(9)ath5k_hw_rf5110_channel(9)ath5k_hw_rf5111_chan2athchan(9)ath5k_hw_rf5111_channel(9)ath5k_hw_rf5112_channel(9)ath5k_hw_rf2425_channel(9)ath5k_hw_channel(9)- PHY Calibration routines(9)
ath5k_hw_read_measured_noise_floor(9)ath5k_hw_init_nfcal_hist(9)ath5k_hw_update_nfcal_hist(9)ath5k_hw_get_median_noise_floor(9)ath5k_hw_update_noise_floor(9)ath5k_hw_rf5110_calibrate(9)ath5k_hw_rf511x_iq_calibrate(9)ath5k_hw_phy_calibrate(9)ath5k_hw_set_spur_mitigation_filter(9)- Antenna control(9)
ath5k_hw_set_def_antenna(9)ath5k_hw_set_fast_div(9)ath5k_hw_set_antenna_switch(9)ath5k_hw_set_antenna_mode(9)ath5k_get_interpolated_value(9)ath5k_get_linear_pcdac_min(9)ath5k_create_power_curve(9)ath5k_get_rate_pcal_data(9)ath5k_get_max_ctl_power(9)- Power to PCDAC table functions(9)
ath5k_fill_pwr_to_pcdac_table(9)ath5k_combine_linear_pcdac_curves(9)ath5k_write_pcdac_table(9)- Power to PDADC table functions(9)
ath5k_combine_pwr_to_pdadc_curves(9)ath5k_write_pwr_to_pdadc_table(9)ath5k_setup_channel_powertable(9)ath5k_write_channel_powertable(9)- Per-rate tx power setting(9)
ath5k_setup_rate_powertable(9)ath5k_hw_txpower(9)ath5k_hw_set_txpower_limit(9)ath5k_hw_phy_init(9)
mwah π this page lives under the source path ./drivers/net/wireless/ath/ath5k and the footer date is October 2026 β go interpolate those surrounding calibration piers, bestie, youβve got this π«Άπ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms