include/linux/soc/mediatek/dvfsrc.h
Source file repositories/reference/linux-study-clean/include/linux/soc/mediatek/dvfsrc.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/soc/mediatek/dvfsrc.h- Extension
.h- Size
- 903 bytes
- Lines
- 37
- 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
- No C-style include directives detected by the generator.
Detected Declarations
enum mtk_dvfsrc_cmdfunction mtk_dvfsrc_send_requestfunction mtk_dvfsrc_query_info
Annotated Snippet
#ifndef __MEDIATEK_DVFSRC_H
#define __MEDIATEK_DVFSRC_H
enum mtk_dvfsrc_cmd {
MTK_DVFSRC_CMD_BW,
MTK_DVFSRC_CMD_HRT_BW,
MTK_DVFSRC_CMD_PEAK_BW,
MTK_DVFSRC_CMD_OPP,
MTK_DVFSRC_CMD_VCORE_LEVEL,
MTK_DVFSRC_CMD_VSCP_LEVEL,
MTK_DVFSRC_CMD_MAX,
};
#if IS_ENABLED(CONFIG_MTK_DVFSRC)
int mtk_dvfsrc_send_request(const struct device *dev, u32 cmd, u64 data);
int mtk_dvfsrc_query_info(const struct device *dev, u32 cmd, int *data);
#else
static inline int mtk_dvfsrc_send_request(const struct device *dev, u32 cmd, u64 data)
{ return -ENODEV; }
static inline int mtk_dvfsrc_query_info(const struct device *dev, u32 cmd, int *data)
{ return -ENODEV; }
#endif /* CONFIG_MTK_DVFSRC */
#endif
Annotation
- Detected declarations: `enum mtk_dvfsrc_cmd`, `function mtk_dvfsrc_send_request`, `function mtk_dvfsrc_query_info`.
- 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.