Documentation/devicetree/bindings/net/mdio-gpio.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/net/mdio-gpio.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/net/mdio-gpio.yaml- Extension
.yaml- Size
- 1068 bytes
- Lines
- 58
- 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/net/mdio-gpio.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: MDIO on GPIOs
maintainers:
- Andrew Lunn <andrew@lunn.ch>
- Heiner Kallweit <hkallweit1@gmail.com>
- Russell King <linux@armlinux.org.uk>
allOf:
- $ref: mdio.yaml#
properties:
compatible:
enum:
- virtual,mdio-gpio
- microchip,mdio-smi0
"#address-cells":
const: 1
"#size-cells":
const: 0
gpios:
minItems: 2
items:
- description: MDC
- description: MDIO
- description: MDO
# Note: Each gpio-mdio bus should have an alias correctly numbered in "aliases"
# node.
additionalProperties:
type: object
examples:
- |
aliases {
mdio-gpio0 = &mdio0;
};
mdio0: mdio {
compatible = "virtual,mdio-gpio";
#address-cells = <1>;
#size-cells = <0>;
gpios = <&qe_pio_a 11>,
<&qe_pio_c 6>;
ethphy0: ethernet-phy@0 {
reg = <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.