arch/mips/include/asm/mach-au1x00/gpio-au1300.h

File Facts

System

Linux kernel

Corpus path

arch/mips/include/asm/mach-au1x00/gpio-au1300.h

Extension

.h

Size

2663 bytes

Lines

121

Domain

Architecture Layer

Bucket

arch/mips

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• asm/addrspace.h
• asm/io.h
• asm/mach-au1x00/au1000.h

Detected Declarations

• struct gpio_chip
• struct software_node
• function au1300_gpio_get_value
• function au1300_gpio_direction_input
• function au1300_gpio_set_value
• function au1300_gpio_direction_output
• function au1300_gpio_to_irq
• function au1300_irq_to_gpio
• function au1300_gpio_is_valid
• function au1300_gpio_getinitlvl

Annotated Snippet

else if (gpio > 31) {
		gpio -= 32;
		roff += 4;
	}

	v = __raw_readl(roff + AU1300_GPIC_RSTVAL);
	return (v >> gpio) & 1;
}

#endif /* _GPIO_AU1300_H_ */

Annotation

• Immediate include surface: `asm/addrspace.h`, `asm/io.h`, `asm/mach-au1x00/au1000.h`.
• Detected declarations: `struct gpio_chip`, `struct software_node`, `function au1300_gpio_get_value`, `function au1300_gpio_direction_input`, `function au1300_gpio_set_value`, `function au1300_gpio_direction_output`, `function au1300_gpio_to_irq`, `function au1300_irq_to_gpio`, `function au1300_gpio_is_valid`, `function au1300_gpio_getinitlvl`.
• Atlas domain: Architecture Layer / arch/mips.
• 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.