arch/m68k/amiga/amisound.c

File Facts

System

Linux kernel

Corpus path

arch/m68k/amiga/amisound.c

Extension

.c

Size

2813 bytes

Lines

119

Domain

Architecture Layer

Bucket

arch/m68k

Inferred role

Architecture Layer: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

• CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/jiffies.h
• linux/timer.h
• linux/init.h
• linux/string.h
• linux/module.h
• asm/amigahw.h
• amiga.h

Detected Declarations

• function amiga_init_sound
• function amiga_mksound
• function nosound
• export amiga_audio_min_period
• export amiga_audio_period

Annotated Snippet

if (ticks) {
			sound_timer.expires = jiffies + ticks;
			add_timer( &sound_timer );
		}

		/* turn on DMA for audio channel 2 */
		custom.dmacon = DMAF_SETCLR | DMAF_AUD2;

	} else
		nosound( 0 );

	local_irq_restore(flags);
}


static void nosound(struct timer_list *unused)
{
	/* turn off DMA for audio channel 2 */
	custom.dmacon = DMAF_AUD2;
	/* restore period to previous value after beeping */
	custom.aud[2].audper = amiga_audio_period;
}

Annotation

• Immediate include surface: `linux/jiffies.h`, `linux/timer.h`, `linux/init.h`, `linux/string.h`, `linux/module.h`, `asm/amigahw.h`, `amiga.h`.
• Detected declarations: `function amiga_init_sound`, `function amiga_mksound`, `function nosound`, `export amiga_audio_min_period`, `export amiga_audio_period`.
• Atlas domain: Architecture Layer / arch/m68k.
• Implementation status: integration 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.