drivers/gpu/drm/omapdrm/omap_fbdev.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/omapdrm/omap_fbdev.h

Extension

.h

Size

747 bytes

Lines

31

Domain

Driver Families

Bucket

drivers/gpu

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 drm_device
• struct drm_fb_helper
• struct drm_fb_helper_surface_size
• function omap_fbdev_setup

Annotated Snippet

#ifndef __OMAPDRM_FBDEV_H__
#define __OMAPDRM_FBDEV_H__

struct drm_device;
struct drm_fb_helper;
struct drm_fb_helper_surface_size;

#ifdef CONFIG_DRM_FBDEV_EMULATION
int omap_fbdev_driver_fbdev_probe(struct drm_fb_helper *helper,
				  struct drm_fb_helper_surface_size *sizes);
#define OMAP_FBDEV_DRIVER_OPS \
	.fbdev_probe = omap_fbdev_driver_fbdev_probe
void omap_fbdev_setup(struct drm_device *dev);
#else
#define OMAP_FBDEV_DRIVER_OPS \
	.fbdev_probe = NULL
static inline void omap_fbdev_setup(struct drm_device *dev)
{
}
#endif

#endif /* __OMAPDRM_FBDEV_H__ */

Annotation

• Detected declarations: `struct drm_device`, `struct drm_fb_helper`, `struct drm_fb_helper_surface_size`, `function omap_fbdev_setup`.
• Atlas domain: Driver Families / drivers/gpu.
• 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.