drivers/net/ethernet/freescale/fman/fman_muram.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/freescale/fman/fman_muram.h

Extension

.h

Size

657 bytes

Lines

27

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

• linux/types.h

Detected Declarations

• struct muram_info

Annotated Snippet

#ifndef __FM_MURAM_EXT
#define __FM_MURAM_EXT

#include <linux/types.h>

#define FM_MURAM_INVALID_ALLOCATION	-1

/* Structure for FM MURAM information */
struct muram_info;

struct muram_info *fman_muram_init(phys_addr_t base, size_t size);

unsigned long fman_muram_offset_to_vbase(struct muram_info *muram,
					 unsigned long offset);

unsigned long fman_muram_alloc(struct muram_info *muram, size_t size);

void fman_muram_free_mem(struct muram_info *muram, unsigned long offset,
			 size_t size);

#endif /* __FM_MURAM_EXT */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct muram_info`.
• 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.