Documentation/devicetree/bindings/pinctrl/brcm,bcm2712c0-pinctrl.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/pinctrl/brcm,bcm2712c0-pinctrl.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/pinctrl/brcm,bcm2712c0-pinctrl.yaml- Extension
.yaml- Size
- 3931 bytes
- Lines
- 138
- 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/brcm,bcm2712c0-pinctrl.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Broadcom STB family pin controller
maintainers:
- Ivan T. Ivanov <iivanov@suse.de>
- A. della Porta <andrea.porta@suse.com>
description: >
Broadcom's STB family of memory-mapped pin controllers.
This includes the pin controllers inside the BCM2712 SoC which
are instances of the STB family and has two silicon variants,
C0 and D0, which differs slightly in terms of registers layout.
The -aon- (Always On) variant is the same IP block but differs
in the number of pins that are associated and the pinmux functions
for each of those pins.
allOf:
- $ref: pinctrl.yaml#
properties:
compatible:
enum:
- brcm,bcm2712c0-pinctrl
- brcm,bcm2712c0-aon-pinctrl
- brcm,bcm2712d0-pinctrl
- brcm,bcm2712d0-aon-pinctrl
reg:
maxItems: 1
patternProperties:
'-state$':
oneOf:
- $ref: '#/$defs/brcmstb-pinctrl-state'
- patternProperties:
'-pins$':
$ref: '#/$defs/brcmstb-pinctrl-state'
additionalProperties: false
$defs:
brcmstb-pinctrl-state:
allOf:
- $ref: pincfg-node.yaml#
- $ref: pinmux-node.yaml#
description: >
Pin controller client devices use pin configuration subnodes (children
and grandchildren) for desired pin configuration.
Client device subnodes use below standard properties.
properties:
pins:
description:
List of gpio pins affected by the properties specified in this
subnode (either this or "groups" must be specified).
items:
pattern: '^((aon_)?s?gpio[0-6]?[0-9])|(emmc_(clk|cmd|dat[0-7]|ds))$'
function:
description:
Specify the alternative function to be configured for the specified
pins.
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.