arch/arm/mach-orion5x/tsx09-common.c

File Facts

System

Linux kernel

Corpus path

arch/arm/mach-orion5x/tsx09-common.c

Extension

.c

Size

2988 bytes

Lines

130

Domain

Architecture Layer

Bucket

arch/arm

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

• linux/kernel.h
• linux/pci.h
• linux/mv643xx_eth.h
• linux/timex.h
• linux/serial_reg.h
• orion5x.h
• tsx09-common.h
• common.h

Detected Declarations

• function qnap_tsx09_power_off
• function qnap_tsx09_parse_hex_nibble
• function qnap_tsx09_parse_hex_byte
• function qnap_tsx09_check_mac_addr
• function qnap_tsx09_find_mac_addr

Annotated Snippet

if (nor_page != NULL) {
			ret = qnap_tsx09_check_mac_addr(nor_page);
			iounmap(nor_page);
		}

		if (ret == 0)
			break;
	}
}

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/pci.h`, `linux/mv643xx_eth.h`, `linux/timex.h`, `linux/serial_reg.h`, `orion5x.h`, `tsx09-common.h`, `common.h`.
• Detected declarations: `function qnap_tsx09_power_off`, `function qnap_tsx09_parse_hex_nibble`, `function qnap_tsx09_parse_hex_byte`, `function qnap_tsx09_check_mac_addr`, `function qnap_tsx09_find_mac_addr`.
• Atlas domain: Architecture Layer / arch/arm.
• 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.