arch/arm/boot/dts/broadcom/bcm-nsp-ax.dtsi

File Facts

System

Linux kernel

Corpus path

arch/arm/boot/dts/broadcom/bcm-nsp-ax.dtsi

Extension

.dtsi

Size

940 bytes

Lines

71

Domain

Architecture Layer

Bucket

arch/arm

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-later OR MIT
/*
 * Broadcom Northstar Plus Ax stepping-specific bindings.
 * Notable differences from B0+ are the secondary-boot-reg and
 * lack of DMA coherency.
 */

&cpu1 {
	secondary-boot-reg = <0xffff042c>;
};

&dma {
	/delete-property/ dma-coherent;
};

&sdio {
	/delete-property/ dma-coherent;
};

&amac0 {
	/delete-property/ dma-coherent;
};

&amac1 {
	/delete-property/ dma-coherent;
};

&amac2 {
	/delete-property/ dma-coherent;
};

&ehci0 {
	/delete-property/ dma-coherent;
};

&mailbox {
	/delete-property/ dma-coherent;
};

&xhci {
	/delete-property/ dma-coherent;
};

&ehci0 {
	/delete-property/ dma-coherent;
};

&ohci0 {
	/delete-property/ dma-coherent;
};

&i2c0 {
	/delete-property/ dma-coherent;
};

&sata {
	/delete-property/ dma-coherent;
};

&pcie0 {
	/delete-property/ dma-coherent;
};

&pcie1 {
	/delete-property/ dma-coherent;
};

&pcie2 {
	/delete-property/ dma-coherent;
};

Annotation

• Atlas domain: Architecture Layer / arch/arm.
• 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.