Documentation/devicetree/bindings/pinctrl/microchip,mpfs-pinctrl-iomux0.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/pinctrl/microchip,mpfs-pinctrl-iomux0.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/pinctrl/microchip,mpfs-pinctrl-iomux0.yaml- Extension
.yaml- Size
- 2380 bytes
- Lines
- 90
- 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/pinctrl/microchip,mpfs-pinctrl-iomux0.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Microchip PolarFire SoC iomux0
maintainers:
- Conor Dooley <conor.dooley@microchip.com>
description:
iomux0 is responsible for routing some functions to either the FPGA fabric,
or to MSSIOs. It only performs muxing, and has no IO configuration role, as
fabric IOs are configured separately and just routing a function to MSSIOs is
not sufficient for it to actually get mapped to an MSSIO, just makes it
possible.
properties:
compatible:
oneOf:
- const: microchip,mpfs-pinctrl-iomux0
- items:
- const: microchip,pic64gx-pinctrl-iomux0
- const: microchip,mpfs-pinctrl-iomux0
reg:
maxItems: 1
pinctrl-use-default: true
patternProperties:
'^mux-':
type: object
$ref: pinmux-node.yaml
additionalProperties: false
properties:
function:
description:
A string containing the name of the function to mux to the group.
enum: [ spi0, spi1, i2c0, i2c1, can0, can1, qspi, uart0, uart1, uart2,
uart3, uart4, mdio0, mdio1 ]
groups:
description:
An array of strings. Each string contains the name of a group.
items:
enum: [ spi0_fabric, spi0_mssio, spi1_fabric, spi1_mssio, i2c0_fabric,
i2c0_mssio, i2c1_fabric, i2c1_mssio, can0_fabric, can0_mssio,
can1_fabric, can1_mssio, qspi_fabric, qspi_mssio,
uart0_fabric, uart0_mssio, uart1_fabric, uart1_mssio,
uart2_fabric, uart2_mssio, uart3_fabric, uart3_mssio,
uart4_fabric, uart4_mssio, mdio0_fabric, mdio0_mssio,
mdio1_fabric, mdio1_mssio ]
required:
- function
- groups
required:
- compatible
- reg
additionalProperties: false
examples:
- |
soc {
#size-cells = <1>;
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.