Documentation/devicetree/bindings/pci/rockchip,rk3399-pcie-common.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/pci/rockchip,rk3399-pcie-common.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/pci/rockchip,rk3399-pcie-common.yaml- Extension
.yaml- Size
- 1104 bytes
- Lines
- 70
- 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 OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/pci/rockchip,rk3399-pcie-common.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Rockchip AXI PCIe Bridge Common Properties
maintainers:
- Shawn Lin <shawn.lin@rock-chips.com>
properties:
reg:
maxItems: 2
clocks:
maxItems: 4
clock-names:
items:
- const: aclk
- const: aclk-perf
- const: hclk
- const: pm
num-lanes:
maximum: 4
phys:
oneOf:
- maxItems: 1
- maxItems: 4
phy-names:
oneOf:
- const: pcie-phy
- items:
- const: pcie-phy-0
- const: pcie-phy-1
- const: pcie-phy-2
- const: pcie-phy-3
resets:
maxItems: 7
reset-names:
items:
- const: core
- const: mgmt
- const: mgmt-sticky
- const: pipe
- const: pm
- const: pclk
- const: aclk
required:
- compatible
- reg
- reg-names
- clocks
- clock-names
- phys
- phy-names
- resets
- reset-names
additionalProperties: true
...
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.