drivers/media/pci/mgb4/mgb4_regs.h

File Facts

System

Linux kernel

Corpus path

drivers/media/pci/mgb4/mgb4_regs.h

Extension

.h

Size

803 bytes

Lines

36

Domain

Driver Families

Bucket

drivers/media

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

• linux/io.h

Detected Declarations

• struct mgb4_regs
• function mgb4_mask_reg

Annotated Snippet

struct mgb4_regs {
	resource_size_t mapbase;
	resource_size_t mapsize;
	void __iomem *membase;
};

#define mgb4_write_reg(regs, offset, val) \
	iowrite32(val, (regs)->membase + (offset))
#define  mgb4_read_reg(regs, offset) \
	ioread32((regs)->membase + (offset))

static inline void mgb4_mask_reg(struct mgb4_regs *regs, u32 reg, u32 mask,
				 u32 val)
{
	u32 ret = mgb4_read_reg(regs, reg);

	val |= ret & ~mask;
	mgb4_write_reg(regs, reg, val);
}

int mgb4_regs_map(struct resource *res, struct mgb4_regs *regs);
void mgb4_regs_free(struct mgb4_regs *regs);

#endif

Annotation

• Immediate include surface: `linux/io.h`.
• Detected declarations: `struct mgb4_regs`, `function mgb4_mask_reg`.
• Atlas domain: Driver Families / drivers/media.
• 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.