drivers/net/ethernet/mucse/rnpgbe/rnpgbe_mbx.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/mucse/rnpgbe/rnpgbe_mbx.h

Extension

.h

Size

750 bytes

Lines

21

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

• rnpgbe.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef _RNPGBE_MBX_H
#define _RNPGBE_MBX_H

#include "rnpgbe.h"

#define MUCSE_MBX_FW2PF_CNT       0
#define MUCSE_MBX_PF2FW_CNT       4
#define MUCSE_MBX_FWPF_SHM        8
#define MUCSE_MBX_PF2FW_CTRL(mbx) ((mbx)->pf2fw_mbx_ctrl)
#define MUCSE_MBX_FWPF_MASK(mbx)  ((mbx)->fwpf_mbx_mask)
#define MUCSE_MBX_REQ             BIT(0) /* Request a req to mailbox */
#define MUCSE_MBX_PFU             BIT(3) /* PF owns the mailbox buffer */

int mucse_write_and_wait_ack_mbx(struct mucse_hw *hw, u32 *msg, u16 size);
void mucse_init_mbx_params_pf(struct mucse_hw *hw);
int mucse_poll_and_read_mbx(struct mucse_hw *hw, u32 *msg, u16 size);
#endif /* _RNPGBE_MBX_H */

Annotation

• Immediate include surface: `rnpgbe.h`.
• 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.