drivers/net/wireless/marvell/mwifiex/sta_cmdresp.c
Source file repositories/reference/linux-study-clean/drivers/net/wireless/marvell/mwifiex/sta_cmdresp.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/wireless/marvell/mwifiex/sta_cmdresp.c- Extension
.c- Size
- 42155 bytes
- Lines
- 1444
- Domain
- Driver Families
- Bucket
- drivers/net
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
decl.hioctl.hutil.hfw.hmain.hwmm.h11n.h11ac.h
Detected Declarations
function mwifiex_process_cmdresp_errorfunction mwifiex_ret_802_11_rssi_infofunction mwifiex_ret_802_11_snmp_mibfunction mwifiex_ret_get_logfunction mwifiex_ret_tx_rate_cfgfunction mwifiex_get_power_levelfunction mwifiex_ret_tx_power_cfgfunction mwifiex_ret_rf_tx_powerfunction mwifiex_ret_rf_antennafunction mwifiex_ret_802_11_mac_addressfunction mwifiex_ret_mac_multicast_adrfunction mwifiex_ret_802_11_tx_rate_queryfunction mwifiex_ret_802_11_deauthenticatefunction mwifiex_ret_802_11_ad_hoc_stopfunction mwifiex_ret_802_11_key_material_v1function mwifiex_ret_802_11_key_material_v2function mwifiex_ret_802_11_key_materialfunction mwifiex_ret_802_11d_domain_infofunction mwifiex_ret_ver_extfunction mwifiex_ret_remain_on_chanfunction mwifiex_ret_p2p_mode_cfgfunction mwifiex_ret_mem_accessfunction mwifiex_ret_reg_accessfunction mwifiex_ret_ibss_coalescing_statusfunction mwifiex_ret_tdls_operfunction mwifiex_ret_subsc_evtfunction mwifiex_ret_uap_sta_listfunction mwifiex_ret_cfg_datafunction mwifiex_ret_sdio_rx_aggr_cfgfunction mwifiex_ret_robust_coexfunction mwifiex_create_custom_regdomainfunction mwifiex_ret_chan_region_cfgfunction mwifiex_ret_pkt_aggr_ctrlfunction mwifiex_ret_get_chan_infofunction mwifiex_process_sta_cmdresp
Annotated Snippet
switch (oid) {
case FRAG_THRESH_I:
mwifiex_dbg(priv->adapter, INFO,
"info: SNMP_RESP: FragThsd =%u\n",
ul_temp);
break;
case RTS_THRESH_I:
mwifiex_dbg(priv->adapter, INFO,
"info: SNMP_RESP: RTSThsd =%u\n",
ul_temp);
break;
case SHORT_RETRY_LIM_I:
mwifiex_dbg(priv->adapter, INFO,
"info: SNMP_RESP: TxRetryCount=%u\n",
ul_temp);
break;
case DTIM_PERIOD_I:
mwifiex_dbg(priv->adapter, INFO,
"info: SNMP_RESP: DTIM period=%u\n",
ul_temp);
break;
default:
break;
}
}
return 0;
}
/*
* This function handles the command response of get log request
*
* Handling includes changing the header fields into CPU format
* and sending the received parameters to application.
*/
static int mwifiex_ret_get_log(struct mwifiex_private *priv,
struct host_cmd_ds_command *resp,
struct mwifiex_ds_get_stats *stats)
{
struct host_cmd_ds_802_11_get_log *get_log =
&resp->params.get_log;
if (stats) {
stats->mcast_tx_frame = le32_to_cpu(get_log->mcast_tx_frame);
stats->failed = le32_to_cpu(get_log->failed);
stats->retry = le32_to_cpu(get_log->retry);
stats->multi_retry = le32_to_cpu(get_log->multi_retry);
stats->frame_dup = le32_to_cpu(get_log->frame_dup);
stats->rts_success = le32_to_cpu(get_log->rts_success);
stats->rts_failure = le32_to_cpu(get_log->rts_failure);
stats->ack_failure = le32_to_cpu(get_log->ack_failure);
stats->rx_frag = le32_to_cpu(get_log->rx_frag);
stats->mcast_rx_frame = le32_to_cpu(get_log->mcast_rx_frame);
stats->fcs_error = le32_to_cpu(get_log->fcs_error);
stats->tx_frame = le32_to_cpu(get_log->tx_frame);
stats->wep_icv_error[0] =
le32_to_cpu(get_log->wep_icv_err_cnt[0]);
stats->wep_icv_error[1] =
le32_to_cpu(get_log->wep_icv_err_cnt[1]);
stats->wep_icv_error[2] =
le32_to_cpu(get_log->wep_icv_err_cnt[2]);
stats->wep_icv_error[3] =
le32_to_cpu(get_log->wep_icv_err_cnt[3]);
stats->bcn_rcv_cnt = le32_to_cpu(get_log->bcn_rcv_cnt);
stats->bcn_miss_cnt = le32_to_cpu(get_log->bcn_miss_cnt);
}
return 0;
}
/*
* This function handles the command response of set/get Tx rate
* configurations.
*
* Handling includes changing the header fields into CPU format
* and saving the following parameters in driver -
* - DSSS rate bitmap
* - OFDM rate bitmap
* - HT MCS rate bitmaps
*
* Based on the new rate bitmaps, the function re-evaluates if
* auto data rate has been activated. If not, it sends another
* query to the firmware to get the current Tx data rate.
*/
static int mwifiex_ret_tx_rate_cfg(struct mwifiex_private *priv,
struct host_cmd_ds_command *resp)
{
struct host_cmd_ds_tx_rate_cfg *rate_cfg = &resp->params.tx_rate_cfg;
struct mwifiex_rate_scope *rate_scope;
struct mwifiex_ie_types_header *head;
Annotation
- Immediate include surface: `decl.h`, `ioctl.h`, `util.h`, `fw.h`, `main.h`, `wmm.h`, `11n.h`, `11ac.h`.
- Detected declarations: `function mwifiex_process_cmdresp_error`, `function mwifiex_ret_802_11_rssi_info`, `function mwifiex_ret_802_11_snmp_mib`, `function mwifiex_ret_get_log`, `function mwifiex_ret_tx_rate_cfg`, `function mwifiex_get_power_level`, `function mwifiex_ret_tx_power_cfg`, `function mwifiex_ret_rf_tx_power`, `function mwifiex_ret_rf_antenna`, `function mwifiex_ret_802_11_mac_address`.
- Atlas domain: Driver Families / drivers/net.
- Implementation status: source implementation candidate.
- Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.