drivers/gpu/drm/verisilicon/vs_dc.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/verisilicon/vs_dc.h

Extension

.h

Size

743 bytes

Lines

39

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

• linux/clk.h
• linux/regmap.h
• linux/reset.h
• drm/drm_device.h
• vs_hwdb.h

Detected Declarations

• struct vs_drm_dev
• struct vs_crtc
• struct vs_dc

Annotated Snippet

struct vs_dc {
	struct regmap *regs;
	struct clk *core_clk;
	struct clk *axi_clk;
	struct clk *ahb_clk;
	struct clk *pix_clk[VSDC_MAX_OUTPUTS];
	struct reset_control_bulk_data rsts[VSDC_RESET_COUNT];

	struct vs_drm_dev *drm_dev;
	struct vs_chip_identity identity;
};

#endif /* _VS_DC_H_ */

Annotation

• Immediate include surface: `linux/clk.h`, `linux/regmap.h`, `linux/reset.h`, `drm/drm_device.h`, `vs_hwdb.h`.
• Detected declarations: `struct vs_drm_dev`, `struct vs_crtc`, `struct vs_dc`.
• 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.