Documentation/devicetree/bindings/phy/marvell,armada-375-usb-cluster.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/phy/marvell,armada-375-usb-cluster.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/phy/marvell,armada-375-usb-cluster.yaml- Extension
.yaml- Size
- 877 bytes
- Lines
- 41
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: configuration, schema, or hardware description
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
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-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/phy/marvell,armada-375-usb-cluster.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Armada 375 USB Cluster
maintainers:
- Andrew Lunn <andrew@lunn.ch>
- Gregory Clement <gregory.clement@bootlin.com>
description:
Control register for the Armada 375 USB cluster, managing USB2 and USB3 features.
properties:
compatible:
const: marvell,armada-375-usb-cluster
reg:
maxItems: 1
'#phy-cells':
description: Number of PHY cells in specifier. 1 for USB2, 2 for USB3.
const: 1
required:
- compatible
- reg
- '#phy-cells'
additionalProperties: false
examples:
- |
usbcluster: usb-cluster@18400 {
compatible = "marvell,armada-375-usb-cluster";
reg = <0x18400 0x4>;
#phy-cells = <1>;
};
Annotation
- Atlas domain: Support Tooling And Documentation / Documentation.
- 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.