drivers/net/ethernet/chelsio/cxgb4/cudbg_entity.h
Source file repositories/reference/linux-study-clean/drivers/net/ethernet/chelsio/cxgb4/cudbg_entity.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/ethernet/chelsio/cxgb4/cudbg_entity.h- Extension
.h- Size
- 6807 bytes
- Lines
- 353
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
struct cudbg_mbox_logstruct cudbg_cim_qcfgstruct cudbg_rss_vf_confstruct cudbg_pm_statsstruct cudbg_hw_schedstruct sge_qbase_reg_fieldstruct ireg_fieldstruct ireg_bufstruct cudbg_ulprx_lastruct cudbg_tp_lastruct cudbg_region_infostruct cudbg_mem_descstruct cudbg_meminfostruct cudbg_cim_pif_lastruct cudbg_clk_infostruct cudbg_tid_info_regionstruct cudbg_tid_info_region_rev1struct cudbg_ch_cntxtstruct cudbg_mps_tcamstruct cudbg_vpd_datastruct cudbg_tcamstruct cudbg_tid_datastruct cudbg_ulptx_lastruct cudbg_pbt_tablesstruct cudbg_qdesc_entrystruct cudbg_qdesc_infoenum cudbg_le_entry_typesenum cudbg_qdesc_qtype
Annotated Snippet
struct cudbg_mbox_log {
struct mbox_cmd entry;
u32 hi[MBOX_LEN / 8];
u32 lo[MBOX_LEN / 8];
};
struct cudbg_cim_qcfg {
u8 chip;
u16 base[CIM_NUM_IBQ + CIM_NUM_OBQ_T5];
u16 size[CIM_NUM_IBQ + CIM_NUM_OBQ_T5];
u16 thres[CIM_NUM_IBQ];
u32 obq_wr[2 * CIM_NUM_OBQ_T5];
u32 stat[4 * (CIM_NUM_IBQ + CIM_NUM_OBQ_T5)];
};
struct cudbg_rss_vf_conf {
u32 rss_vf_vfl;
u32 rss_vf_vfh;
};
struct cudbg_pm_stats {
u32 tx_cnt[T6_PM_NSTATS];
u32 rx_cnt[T6_PM_NSTATS];
u64 tx_cyc[T6_PM_NSTATS];
u64 rx_cyc[T6_PM_NSTATS];
};
struct cudbg_hw_sched {
u32 kbps[NTX_SCHED];
u32 ipg[NTX_SCHED];
u32 pace_tab[NTX_SCHED];
u32 mode;
u32 map;
};
#define SGE_QBASE_DATA_REG_NUM 4
struct sge_qbase_reg_field {
u32 reg_addr;
u32 reg_data[SGE_QBASE_DATA_REG_NUM];
/* Max supported PFs */
u32 pf_data_value[PCIE_FW_MASTER_M + 1][SGE_QBASE_DATA_REG_NUM];
/* Max supported VFs */
u32 vf_data_value[T6_VF_M + 1][SGE_QBASE_DATA_REG_NUM];
u32 vfcount; /* Actual number of max vfs in current configuration */
};
struct ireg_field {
u32 ireg_addr;
u32 ireg_data;
u32 ireg_local_offset;
u32 ireg_offset_range;
};
struct ireg_buf {
struct ireg_field tp_pio;
u32 outbuf[32];
};
struct cudbg_ulprx_la {
u32 data[ULPRX_LA_SIZE * 8];
u32 size;
};
struct cudbg_tp_la {
u32 size;
u32 mode;
u8 data[];
};
static const char * const cudbg_region[] = {
"DBQ contexts:", "IMSG contexts:", "FLM cache:", "TCBs:",
"Pstructs:", "Timers:", "Rx FL:", "Tx FL:", "Pstruct FL:",
"Tx payload:", "Rx payload:", "LE hash:", "iSCSI region:",
"TDDP region:", "TPT region:", "STAG region:", "RQ region:",
"RQUDP region:", "PBL region:", "TXPBL region:",
"DBVFIFO region:", "ULPRX state:", "ULPTX state:",
"On-chip queues:"
};
/* Memory region info relative to current memory (i.e. wrt 0). */
struct cudbg_region_info {
bool exist; /* Does region exists in current memory? */
u32 start; /* Start wrt 0 */
u32 end; /* End wrt 0 */
};
struct cudbg_mem_desc {
u32 base;
u32 limit;
Annotation
- Detected declarations: `struct cudbg_mbox_log`, `struct cudbg_cim_qcfg`, `struct cudbg_rss_vf_conf`, `struct cudbg_pm_stats`, `struct cudbg_hw_sched`, `struct sge_qbase_reg_field`, `struct ireg_field`, `struct ireg_buf`, `struct cudbg_ulprx_la`, `struct cudbg_tp_la`.
- Atlas domain: Driver Families / drivers/net.
- Implementation status: source implementation candidate.
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.