blob: 3b40e271fe8d858d250a562bba360906f8320c8c (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
|
# 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>;
};
|
