drivers/video/fbdev/mmp/fb/mmpfb.h
Source file repositories/reference/linux-study-clean/drivers/video/fbdev/mmp/fb/mmpfb.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/video/fbdev/mmp/fb/mmpfb.h- Extension
.h- Size
- 828 bytes
- Lines
- 42
- Domain
- Driver Families
- Bucket
- drivers/video
- 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
video/mmp_disp.hlinux/fb.h
Detected Declarations
struct mmpfb_info
Annotated Snippet
struct mmpfb_info {
struct device *dev;
int id;
const char *name;
struct fb_info *fb_info;
/* basicaly videomode is for output */
struct fb_videomode mode;
int pix_fmt;
void *fb_start;
int fb_size;
dma_addr_t fb_start_dma;
struct mmp_overlay *overlay;
struct mmp_path *path;
struct mutex access_ok;
unsigned int pseudo_palette[16];
int output_fmt;
};
#define MMPFB_DEFAULT_SIZE (PAGE_ALIGN(1920 * 1080 * 4 * 2))
#endif /* _MMP_FB_H_ */
Annotation
- Immediate include surface: `video/mmp_disp.h`, `linux/fb.h`.
- Detected declarations: `struct mmpfb_info`.
- Atlas domain: Driver Families / drivers/video.
- 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.