include/linux/platform_data/shmob_drm.h

File Facts

System

Linux kernel

Corpus path

include/linux/platform_data/shmob_drm.h

Extension

.h

Size

822 bytes

Lines

39

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• video/videomode.h

Detected Declarations

• struct shmob_drm_panel_data
• struct shmob_drm_interface_data
• struct shmob_drm_platform_data
• enum shmob_drm_clk_source

Annotated Snippet

struct shmob_drm_panel_data {
	unsigned int width_mm;		/* Panel width in mm */
	unsigned int height_mm;		/* Panel height in mm */
	struct videomode mode;
};

struct shmob_drm_interface_data {
	unsigned int bus_fmt;		/* MEDIA_BUS_FMT_* */
	unsigned int clk_div;
};

struct shmob_drm_platform_data {
	enum shmob_drm_clk_source clk_source;
	struct shmob_drm_interface_data iface;
	struct shmob_drm_panel_data panel;
};

#endif /* __SHMOB_DRM_H__ */

Annotation

• Immediate include surface: `video/videomode.h`.
• Detected declarations: `struct shmob_drm_panel_data`, `struct shmob_drm_interface_data`, `struct shmob_drm_platform_data`, `enum shmob_drm_clk_source`.
• Atlas domain: Core OS / Core Kernel Interface.
• 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.