Documentation/devicetree/bindings/arm/marvell/marvell,orion5x.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/arm/marvell/marvell,orion5x.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/arm/marvell/marvell,orion5x.yaml- Extension
.yaml- Size
- 989 bytes
- Lines
- 38
- 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/arm/marvell/marvell,orion5x.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Marvell Orion5x SoC Family
maintainers:
- Andrew Lunn <andrew@lunn.ch>
- Gregory Clement <gregory.clement@bootlin.com>
properties:
$nodename:
const: '/'
compatible:
oneOf:
- items:
- enum:
- netgear,wnr854t
- const: marvell,orion5x-88f5181
- const: marvell,orion5x
- items:
- enum:
- buffalo,kurobox-pro
- buffalo,lschl
- buffalo,lsgl
- buffalo,lswsgl
- buffalo,lswtgl
- lacie,ethernet-disk-mini-v2
- lacie,d2-network
- marvell,rd-88f5182-nas
- maxtor,shared-storage-2
- const: marvell,orion5x-88f5182
- const: marvell,orion5x
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.