include/dt-bindings/clock/qcom,qcs615-videocc.h

File Facts

System

Linux kernel

Corpus path

include/dt-bindings/clock/qcom,qcs615-videocc.h

Extension

.h

Size

845 bytes

Lines

31

Domain

Repository Root And Misc

Bucket

include

Inferred role

Repository Root And Misc: implementation source

Status

source implementation candidate

Why This File Exists

Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.

• Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.

Dependency Surface

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

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef _DT_BINDINGS_CLK_QCOM_VIDEO_CC_QCS615_H
#define _DT_BINDINGS_CLK_QCOM_VIDEO_CC_QCS615_H

/* VIDEO_CC clocks */
#define VIDEO_CC_SLEEP_CLK					0
#define VIDEO_CC_SLEEP_CLK_SRC					1
#define VIDEO_CC_VCODEC0_AXI_CLK				2
#define VIDEO_CC_VCODEC0_CORE_CLK				3
#define VIDEO_CC_VENUS_AHB_CLK					4
#define VIDEO_CC_VENUS_CLK_SRC					5
#define VIDEO_CC_VENUS_CTL_AXI_CLK				6
#define VIDEO_CC_VENUS_CTL_CORE_CLK				7
#define VIDEO_CC_XO_CLK						8
#define VIDEO_PLL0						9

/* VIDEO_CC power domains */
#define VCODEC0_GDSC						0
#define VENUS_GDSC						1

/* VIDEO_CC resets */
#define VIDEO_CC_INTERFACE_BCR					0
#define VIDEO_CC_VCODEC0_BCR					1
#define VIDEO_CC_VENUS_BCR					2

#endif

Annotation

• Atlas domain: Repository Root And Misc / include.
• 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.