Documentation/devicetree/bindings/phy/sophgo,cv1800b-usb2-phy.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/phy/sophgo,cv1800b-usb2-phy.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/phy/sophgo,cv1800b-usb2-phy.yaml- Extension
.yaml- Size
- 990 bytes
- Lines
- 55
- 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/sophgo,cv1800b-usb2-phy.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Sophgo CV18XX/SG200X USB 2.0 PHY
maintainers:
- Inochi Amaoto <inochiama@gmail.com>
properties:
compatible:
const: sophgo,cv1800b-usb2-phy
reg:
maxItems: 1
"#phy-cells":
const: 0
clocks:
items:
- description: PHY app clock
- description: PHY stb clock
- description: PHY lpm clock
clock-names:
items:
- const: app
- const: stb
- const: lpm
resets:
maxItems: 1
required:
- compatible
- "#phy-cells"
- clocks
- clock-names
additionalProperties: false
examples:
- |
phy@48 {
compatible = "sophgo,cv1800b-usb2-phy";
reg = <0x48 0x4>;
#phy-cells = <0>;
clocks = <&clk 93>, <&clk 94>, <&clk 95>;
clock-names = "app", "stb", "lpm";
resets = <&rst 58>;
};
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.