arch/mips/include/asm/octeon/cvmx-pemx-defs.h
Source file repositories/reference/linux-study-clean/arch/mips/include/asm/octeon/cvmx-pemx-defs.h
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/include/asm/octeon/cvmx-pemx-defs.h- Extension
.h- Size
- 15316 bytes
- Lines
- 652
- Domain
- Architecture Layer
- Bucket
- arch/mips
- Inferred role
- Architecture Layer: implementation source
- Status
- source implementation candidate
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- 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 cvmx_pemx_bar1_indexx_sstruct cvmx_pemx_bar2_mask_sstruct cvmx_pemx_bar_ctl_sstruct cvmx_pemx_bist_status_sstruct cvmx_pemx_bist_status2_sstruct cvmx_pemx_cfg_rd_sstruct cvmx_pemx_cfg_wr_sstruct cvmx_pemx_cpl_lut_valid_sstruct cvmx_pemx_ctl_status_sstruct cvmx_pemx_dbg_info_sstruct cvmx_pemx_dbg_info_en_sstruct cvmx_pemx_diag_status_sstruct cvmx_pemx_inb_read_credits_sstruct cvmx_pemx_int_enb_sstruct cvmx_pemx_int_enb_int_sstruct cvmx_pemx_int_sum_sstruct cvmx_pemx_p2n_bar0_start_sstruct cvmx_pemx_p2n_bar1_start_sstruct cvmx_pemx_p2n_bar2_start_sstruct cvmx_pemx_p2p_barx_end_sstruct cvmx_pemx_p2p_barx_start_sstruct cvmx_pemx_tlp_credits_sstruct cvmx_pemx_tlp_credits_cn61xx
Annotated Snippet
struct cvmx_pemx_bar1_indexx_s {
#ifdef __BIG_ENDIAN_BITFIELD
uint64_t reserved_20_63:44;
uint64_t addr_idx:16;
uint64_t ca:1;
uint64_t end_swp:2;
uint64_t addr_v:1;
#else
uint64_t addr_v:1;
uint64_t end_swp:2;
uint64_t ca:1;
uint64_t addr_idx:16;
uint64_t reserved_20_63:44;
#endif
} s;
};
union cvmx_pemx_bar2_mask {
uint64_t u64;
struct cvmx_pemx_bar2_mask_s {
#ifdef __BIG_ENDIAN_BITFIELD
uint64_t reserved_38_63:26;
uint64_t mask:35;
uint64_t reserved_0_2:3;
#else
uint64_t reserved_0_2:3;
uint64_t mask:35;
uint64_t reserved_38_63:26;
#endif
} s;
};
union cvmx_pemx_bar_ctl {
uint64_t u64;
struct cvmx_pemx_bar_ctl_s {
#ifdef __BIG_ENDIAN_BITFIELD
uint64_t reserved_7_63:57;
uint64_t bar1_siz:3;
uint64_t bar2_enb:1;
uint64_t bar2_esx:2;
uint64_t bar2_cax:1;
#else
uint64_t bar2_cax:1;
uint64_t bar2_esx:2;
uint64_t bar2_enb:1;
uint64_t bar1_siz:3;
uint64_t reserved_7_63:57;
#endif
} s;
};
union cvmx_pemx_bist_status {
uint64_t u64;
struct cvmx_pemx_bist_status_s {
#ifdef __BIG_ENDIAN_BITFIELD
uint64_t reserved_8_63:56;
uint64_t retry:1;
uint64_t rqdata0:1;
uint64_t rqdata1:1;
uint64_t rqdata2:1;
uint64_t rqdata3:1;
uint64_t rqhdr1:1;
uint64_t rqhdr0:1;
uint64_t sot:1;
#else
uint64_t sot:1;
uint64_t rqhdr0:1;
uint64_t rqhdr1:1;
uint64_t rqdata3:1;
uint64_t rqdata2:1;
uint64_t rqdata1:1;
uint64_t rqdata0:1;
uint64_t retry:1;
uint64_t reserved_8_63:56;
#endif
} s;
};
union cvmx_pemx_bist_status2 {
uint64_t u64;
struct cvmx_pemx_bist_status2_s {
#ifdef __BIG_ENDIAN_BITFIELD
uint64_t reserved_10_63:54;
uint64_t e2p_cpl:1;
uint64_t e2p_n:1;
uint64_t e2p_p:1;
uint64_t peai_p2e:1;
uint64_t pef_tpf1:1;
uint64_t pef_tpf0:1;
uint64_t pef_tnf:1;
Annotation
- Detected declarations: `struct cvmx_pemx_bar1_indexx_s`, `struct cvmx_pemx_bar2_mask_s`, `struct cvmx_pemx_bar_ctl_s`, `struct cvmx_pemx_bist_status_s`, `struct cvmx_pemx_bist_status2_s`, `struct cvmx_pemx_cfg_rd_s`, `struct cvmx_pemx_cfg_wr_s`, `struct cvmx_pemx_cpl_lut_valid_s`, `struct cvmx_pemx_ctl_status_s`, `struct cvmx_pemx_dbg_info_s`.
- Atlas domain: Architecture Layer / arch/mips.
- 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.