Documentation/devicetree/bindings/phy/qca,ar7100-usb-phy.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/phy/qca,ar7100-usb-phy.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/phy/qca,ar7100-usb-phy.yaml- Extension
.yaml- Size
- 1006 bytes
- Lines
- 50
- 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/qca,ar7100-usb-phy.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Atheros AR71XX/9XXX USB PHY
maintainers:
- Alban Bedel <albeu@free.fr>
properties:
compatible:
items:
- const: qca,ar7100-usb-phy
reset-names:
description: Names of reset lines in order.
minItems: 1
items:
- const: phy
- const: suspend-override
resets:
description: References to the reset controllers.
minItems: 1
items:
- description: Reset controller for phy
- description: Reset controller for suspend-override
'#phy-cells':
const: 0
required:
- compatible
- reset-names
- resets
- '#phy-cells'
additionalProperties: false
examples:
- |
usb-phy {
compatible = "qca,ar7100-usb-phy";
reset-names = "phy", "suspend-override";
resets = <&rst 4>, <&rst 3>;
#phy-cells = <0>;
};
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.