sound/soc/qcom/usb_offload_utils.h

File Facts

System

Linux kernel

Corpus path

sound/soc/qcom/usb_offload_utils.h

Extension

.h

Size

912 bytes

Lines

31

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

• sound/soc.h

Detected Declarations

• function qcom_snd_usb_offload_jack_setup
• function qcom_snd_usb_offload_jack_remove

Annotated Snippet

#ifndef __QCOM_SND_USB_OFFLOAD_UTILS_H__
#define __QCOM_SND_USB_OFFLOAD_UTILS_H__

#include <sound/soc.h>

#if IS_ENABLED(CONFIG_SND_SOC_QCOM_OFFLOAD_UTILS)
int qcom_snd_usb_offload_jack_setup(struct snd_soc_pcm_runtime *rtd,
				    struct snd_soc_jack *jack, bool *jack_setup);

int qcom_snd_usb_offload_jack_remove(struct snd_soc_pcm_runtime *rtd,
				     bool *jack_setup);
#else
static inline int qcom_snd_usb_offload_jack_setup(struct snd_soc_pcm_runtime *rtd,
						  struct snd_soc_jack *jack,
						  bool *jack_setup)
{
	return -ENODEV;
}

static inline int qcom_snd_usb_offload_jack_remove(struct snd_soc_pcm_runtime *rtd,
						   bool *jack_setup)
{
	return -ENODEV;
}
#endif /* IS_ENABLED(CONFIG_SND_SOC_QCOM_OFFLOAD_UTILS) */
#endif /* __QCOM_SND_USB_OFFLOAD_UTILS_H__ */

Annotation

• Immediate include surface: `sound/soc.h`.
• Detected declarations: `function qcom_snd_usb_offload_jack_setup`, `function qcom_snd_usb_offload_jack_remove`.
• 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.