drivers/mtd/devices/bcm47xxsflash.h
Source file repositories/reference/linux-study-clean/drivers/mtd/devices/bcm47xxsflash.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/mtd/devices/bcm47xxsflash.h- Extension
.h- Size
- 2598 bytes
- Lines
- 82
- Domain
- Driver Families
- Bucket
- drivers/mtd
- 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/mtd/mtd.h
Detected Declarations
struct bcma_drv_ccstruct bcm47xxsflashenum bcm47xxsflash_type
Annotated Snippet
struct bcm47xxsflash {
struct bcma_drv_cc *bcma_cc;
int (*cc_read)(struct bcm47xxsflash *b47s, u16 offset);
void (*cc_write)(struct bcm47xxsflash *b47s, u16 offset, u32 value);
enum bcm47xxsflash_type type;
void __iomem *window;
u32 blocksize;
u16 numblocks;
u32 size;
struct mtd_info mtd;
};
#endif /* BCM47XXSFLASH */
Annotation
- Immediate include surface: `linux/mtd/mtd.h`.
- Detected declarations: `struct bcma_drv_cc`, `struct bcm47xxsflash`, `enum bcm47xxsflash_type`.
- Atlas domain: Driver Families / drivers/mtd.
- 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.