include/sound/sdca_hid.h

File Facts

System

Linux kernel

Corpus path

include/sound/sdca_hid.h

Extension

.h

Size

788 bytes

Lines

39

Domain

Driver Families

Bucket

include/sound

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 device
• struct sdw_slave
• struct sdca_entity
• struct sdca_interrupt
• function sdca_add_hid_device
• function sdca_hid_process_report

Annotated Snippet

#ifndef __SDCA_HID_H__
#define __SDCA_HID_H__

struct device;
struct sdw_slave;

struct sdca_entity;
struct sdca_interrupt;

#if IS_ENABLED(CONFIG_SND_SOC_SDCA_HID)

int sdca_add_hid_device(struct device *dev, struct sdw_slave *sdw,
			struct sdca_entity *entity);
int sdca_hid_process_report(struct sdca_interrupt *interrupt);

#else

static inline int sdca_add_hid_device(struct device *dev, struct sdw_slave *sdw,
				      struct sdca_entity *entity)
{
	return 0;
}

static inline int sdca_hid_process_report(struct sdca_interrupt *interrupt)
{
	return 0;
}

#endif

#endif /* __SDCA_HID_H__ */

Annotation

• Detected declarations: `struct device`, `struct sdw_slave`, `struct sdca_entity`, `struct sdca_interrupt`, `function sdca_add_hid_device`, `function sdca_hid_process_report`.
• Atlas domain: Driver Families / include/sound.
• 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.