arch/sh/include/cpu-sh3/cpu/dac.h

File Facts

System

Linux kernel

Corpus path

arch/sh/include/cpu-sh3/cpu/dac.h

Extension

.h

Size

832 bytes

Lines

45

Domain

Architecture Layer

Bucket

arch/sh

Inferred role

Architecture Layer: implementation source

Status

source 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.

Dependency Surface

• linux/io.h

Detected Declarations

• function Copyright
• function sh_dac_disable
• function sh_dac_output

Annotated Snippet

#ifndef __ASM_CPU_SH3_DAC_H
#define __ASM_CPU_SH3_DAC_H

#include <linux/io.h>

/*
 * Copyright (C) 2003  Andriy Skulysh
 */


#define DADR0	0xa40000a0
#define DADR1	0xa40000a2
#define DACR	0xa40000a4
#define DACR_DAOE1	0x80
#define DACR_DAOE0	0x40
#define DACR_DAE	0x20


static __inline__ void sh_dac_enable(int channel)
{
	unsigned char v;
	v = __raw_readb(DACR);
	if(channel) v |= DACR_DAOE1;
	else v |= DACR_DAOE0;
	__raw_writeb(v,DACR);
}

static __inline__ void sh_dac_disable(int channel)
{
	unsigned char v;
	v = __raw_readb(DACR);
	if(channel) v &= ~DACR_DAOE1;
	else v &= ~DACR_DAOE0;
	__raw_writeb(v,DACR);
}

static __inline__ void sh_dac_output(u8 value, int channel)
{
	if(channel) __raw_writeb(value,DADR1);
	else __raw_writeb(value,DADR0);
}

#endif /* __ASM_CPU_SH3_DAC_H */

Annotation

• Immediate include surface: `linux/io.h`.
• Detected declarations: `function Copyright`, `function sh_dac_disable`, `function sh_dac_output`.
• Atlas domain: Architecture Layer / arch/sh.
• 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.