arch/arm64/boot/dts/apple/t8122-usbpd-i2c.dtsi

File Facts

System

Linux kernel

Corpus path

arch/arm64/boot/dts/apple/t8122-usbpd-i2c.dtsi

Extension

.dtsi

Size

770 bytes

Lines

33

Domain

Architecture Layer

Bucket

arch/arm64

Inferred role

Architecture Layer: configuration, schema, or hardware description

Status

atlas-only

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

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0+ OR MIT
/*
 * Apple M3 MacBook Pro and iMac (M3, 2023) I2C based USB PD controller nodes
 *
 * This file contains nodes for t8122 devices using I2C based cd321x USB Type-C
 * port controllers. The are used in the M3 MacBook Pro and iMacs but not in the
 * M3 Macbook Airs.
 *
 * target-type: J433, J434, J504
 *
 * Copyright The Asahi Linux Contributors
 */

&i2c0 {
	status = "okay";

	hpm0: usb-pd@38 {
		compatible = "apple,cd321x";
		reg = <0x38>;
		interrupt-parent = <&pinctrl_ap>;
		interrupts = <8 IRQ_TYPE_LEVEL_LOW>;
		interrupt-names = "irq";
	};

	hpm1: usb-pd@3f {
		compatible = "apple,cd321x";
		reg = <0x3f>;
		interrupt-parent = <&pinctrl_ap>;
		interrupts = <8 IRQ_TYPE_LEVEL_LOW>;
		interrupt-names = "irq";
	};
};

Annotation

• Atlas domain: Architecture Layer / arch/arm64.
• Implementation status: atlas-only.

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.