sound/soc/qcom/qdsp6/q6adm.h
Source file repositories/reference/linux-study-clean/sound/soc/qcom/qdsp6/q6adm.h
File Facts
- System
- Linux kernel
- Corpus path
sound/soc/qcom/qdsp6/q6adm.h- Extension
.h- Size
- 818 bytes
- Lines
- 28
- Domain
- Driver Families
- Bucket
- sound/soc
- 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 route_payloadstruct q6copp
Annotated Snippet
struct route_payload {
int num_copps;
int session_id;
int copp_idx[MAX_COPPS_PER_PORT];
int port_id[MAX_COPPS_PER_PORT];
};
struct q6copp;
struct q6copp *q6adm_open(struct device *dev, int port_id, int path, int rate,
int channel_mode, int topology, int perf_mode,
uint16_t bit_width, int app_type, int acdb_id);
int q6adm_close(struct device *dev, struct q6copp *copp);
int q6adm_get_copp_id(struct q6copp *copp);
int q6adm_matrix_map(struct device *dev, int path,
struct route_payload payload_map, int perf_mode);
#endif /* __Q6_ADM_V2_H__ */
Annotation
- Detected declarations: `struct route_payload`, `struct q6copp`.
- Atlas domain: Driver Families / sound/soc.
- 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.