arch/arm64/boot/dts/ti/k3-am642-hummingboard-t-usb3.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/ti/k3-am642-hummingboard-t-usb3.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/ti/k3-am642-hummingboard-t-usb3.dts- Extension
.dts- Size
- 781 bytes
- Lines
- 48
- 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
k3-am642-hummingboard-t.dtsk3-serdes.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0+
/*
* Copyright (C) 2023 Josua Mayer <josua@solid-run.com>
*
* DTS for SolidRun AM642 HummingBoard-T,
* running on Cortex A53, with USB-3.1 Gen 1.
*
*/
#include "k3-am642-hummingboard-t.dts"
#include "k3-serdes.h"
/ {
model = "SolidRun AM642 HummingBoard-T with USB-3.1 Gen 1";
};
&serdes0 {
#address-cells = <1>;
#size-cells = <0>;
serdes0_link: phy@0 {
reg = <0>;
cdns,num-lanes = <1>;
cdns,phy-type = <PHY_TYPE_USB3>;
#phy-cells = <0>;
resets = <&serdes_wiz0 1>;
};
};
&serdes_ln_ctrl {
idle-states = <AM64_SERDES0_LANE0_USB>;
};
&serdes_mux {
idle-state = <0>;
};
&usbss0 {
/delete-property/ ti,usb2-only;
};
&usb0 {
maximum-speed = "super-speed";
phys = <&serdes0_link>;
phy-names = "cdns3,usb3-phy";
};
Annotation
- Immediate include surface: `k3-am642-hummingboard-t.dts`, `k3-serdes.h`.
- 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.