Documentation/devicetree/bindings/pwm/pwm-nexus-node.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/pwm/pwm-nexus-node.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/pwm/pwm-nexus-node.yaml- Extension
.yaml- Size
- 1671 bytes
- Lines
- 66
- 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/pwm/pwm-nexus-node.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: PWM Nexus node properties
description: >
Platforms can have a standardized connector/expansion slot that exposes PWMs
signals to expansion boards.
A nexus node allows to remap a phandle list in a consumer node through a
connector node in a generic way. With this remapping, the consumer node needs
to know only about the nexus node. Resources behind the nexus node are
decoupled by the nexus node itself.
maintainers:
- Herve Codina <herve.codina@bootlin.com>
select: true
properties:
'#pwm-cells': true
pwm-map:
$ref: /schemas/types.yaml#/definitions/uint32-matrix
pwm-map-mask:
$ref: /schemas/types.yaml#/definitions/uint32-array
pwm-map-pass-thru:
$ref: /schemas/types.yaml#/definitions/uint32-array
dependentRequired:
pwm-map: ['#pwm-cells']
pwm-map-mask: [ pwm-map ]
pwm-map-pass-thru: [ pwm-map ]
additionalProperties: true
examples:
- |
pwm1: pwm@100 {
reg = <0x100 0x10>;
#pwm-cells = <3>;
};
pwm2: pwm@200 {
reg = <0x200 0x10>;
#pwm-cells = <3>;
};
connector: connector {
#pwm-cells = <3>;
pwm-map = <0 0 0 &pwm1 1 0 0>,
<1 0 0 &pwm2 4 0 0>,
<2 0 0 &pwm1 3 0 0>;
pwm-map-mask = <0xffffffff 0x0 0x0>;
pwm-map-pass-thru = <0x0 0xffffffff 0xffffffff>;
};
device {
pwms = <&connector 1 57000 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.