arch/arm64/boot/dts/socionext/uniphier-pxs3-ref-gadget1.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/socionext/uniphier-pxs3-ref-gadget1.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/socionext/uniphier-pxs3-ref-gadget1.dts- Extension
.dts- Size
- 834 bytes
- Lines
- 41
- 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
uniphier-pxs3-ref.dts
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
//
// Device Tree Source for UniPhier PXs3 Reference Board (for USB-Device #1)
//
// Copyright (C) 2021 Socionext Inc.
// Author: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
/dts-v1/;
#include "uniphier-pxs3-ref.dts"
/ {
model = "UniPhier PXs3 Reference Board (USB-Device #1)";
};
/* I2C3 pinctrl is shared with USB*VBUSIN */
&i2c3 {
status = "disabled";
};
&usb1 {
status = "okay";
dr_mode = "peripheral";
pinctrl-0 = <&pinctrl_usb1_device>;
snps,dis_enblslpm_quirk;
snps,dis_u2_susphy_quirk;
snps,dis_u3_susphy_quirk;
snps,usb2-gadget-lpm-disable;
phy-names = "usb2-phy", "usb3-phy";
phys = <&usb1_hsphy0>, <&usb1_ssphy0>;
};
&usb1_hsphy0 {
/delete-property/ vbus-supply;
};
&usb1_ssphy0 {
/delete-property/ vbus-supply;
};
/delete-node/ &usb1_hsphy1;
Annotation
- Immediate include surface: `uniphier-pxs3-ref.dts`.
- 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.