Documentation/devicetree/bindings/phy/marvell,mmp3-hsic-phy.yaml

File Facts

System

Linux kernel

Corpus path

Documentation/devicetree/bindings/phy/marvell,mmp3-hsic-phy.yaml

Extension

.yaml

Size

730 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-or-later OR BSD-2-Clause)
# Copyright 2019 Lubomir Rintel <lkundrak@v3.sk>
%YAML 1.2
---
$id: http://devicetree.org/schemas/phy/marvell,mmp3-hsic-phy.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: Marvell MMP3 HSIC PHY

maintainers:
  - Lubomir Rintel <lkundrak@v3.sk>

properties:
  compatible:
    const: marvell,mmp3-hsic-phy

  reg:
    maxItems: 1
    description: base address of the device

  "#phy-cells":
    const: 0

required:
  - compatible
  - reg
  - "#phy-cells"

additionalProperties: false

examples:
  - |
    hsic-phy@f0001800 {
            compatible = "marvell,mmp3-hsic-phy";
            reg = <0xf0001800 0x40>;
            #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.