sound/parisc/harmony.c

File Facts

System

Linux kernel

Corpus path

sound/parisc/harmony.c

Extension

.c

Size

23708 bytes

Lines

967

Domain

Driver Families

Bucket

sound/parisc

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/init.h
• linux/slab.h
• linux/time.h
• linux/wait.h
• linux/delay.h
• linux/module.h
• linux/interrupt.h
• linux/spinlock.h
• linux/dma-mapping.h
• linux/io.h
• sound/core.h
• sound/pcm.h
• sound/control.h
• sound/rawmidi.h
• sound/initval.h
• sound/info.h
• asm/hardware.h
• asm/parisc-device.h
• harmony.h

Detected Declarations

• function harmony_read
• function harmony_write
• function harmony_wait_for_control
• function harmony_reset
• function harmony_disable_interrupts
• function harmony_enable_interrupts
• function harmony_mute
• function harmony_unmute
• function harmony_set_control
• function snd_harmony_interrupt
• function scoped_guard
• function scoped_guard
• function scoped_guard
• function scoped_guard
• function snd_harmony_rate_bits
• function snd_harmony_playback_trigger
• function snd_harmony_capture_trigger
• function snd_harmony_set_data_format
• function snd_harmony_playback_prepare
• function snd_harmony_capture_prepare
• function snd_harmony_playback_pointer
• function snd_harmony_capture_pointer
• function snd_harmony_playback_open
• function snd_harmony_capture_open
• function snd_harmony_playback_close
• function snd_harmony_capture_close
• function snd_harmony_pcm_init
• function snd_harmony_set_new_gain
• function snd_harmony_mixercontrol_info
• function snd_harmony_volume_get
• function snd_harmony_volume_put
• function snd_harmony_captureroute_info
• function snd_harmony_captureroute_get
• function snd_harmony_captureroute_put
• function snd_harmony_mixer_reset
• function snd_harmony_mixer_init
• function snd_harmony_free
• function snd_harmony_dev_free
• function snd_harmony_create
• function snd_harmony_probe
• function snd_harmony_remove
• function alsa_harmony_init
• function alsa_harmony_fini
• module init alsa_harmony_init

Annotated Snippet

module_init(alsa_harmony_init);
module_exit(alsa_harmony_fini);

Annotation

• Immediate include surface: `linux/init.h`, `linux/slab.h`, `linux/time.h`, `linux/wait.h`, `linux/delay.h`, `linux/module.h`, `linux/interrupt.h`, `linux/spinlock.h`.
• Detected declarations: `function harmony_read`, `function harmony_write`, `function harmony_wait_for_control`, `function harmony_reset`, `function harmony_disable_interrupts`, `function harmony_enable_interrupts`, `function harmony_mute`, `function harmony_unmute`, `function harmony_set_control`, `function snd_harmony_interrupt`.
• Atlas domain: Driver Families / sound/parisc.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.