drivers/video/fbdev/geode/geodefb.h

File Facts

System

Linux kernel

Corpus path

drivers/video/fbdev/geode/geodefb.h

Extension

.h

Size

846 bytes

Lines

35

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct geodefb_info
• struct geode_dc_ops
• struct geode_vid_ops
• struct geodefb_par

Annotated Snippet

struct geode_dc_ops {
	void (*set_mode)(struct fb_info *);
	void (*set_palette_reg)(struct fb_info *, unsigned, unsigned, unsigned, unsigned);
};

struct geode_vid_ops {
	void (*set_dclk)(struct fb_info *);
	void (*configure_display)(struct fb_info *);
	int  (*blank_display)(struct fb_info *, int blank_mode);
};

struct geodefb_par {
	int enable_crt;
	int panel_x; /* dimensions of an attached flat panel, non-zero => enable panel */
	int panel_y;
	void __iomem *dc_regs;
	void __iomem *vid_regs;
	const struct geode_dc_ops  *dc_ops;
	const struct geode_vid_ops *vid_ops;
};

#endif /* !__GEODEFB_H__ */

Annotation

• Detected declarations: `struct geodefb_info`, `struct geode_dc_ops`, `struct geode_vid_ops`, `struct geodefb_par`.
• 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.