pwm: Add support for pwm nexus node
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest2 patches 7 repliesIn review
- v21 patch 3 repliesSuperseded
- v11 patch 1 replySuperseded
Changes in v3 from the cover letter
- Patch 1 (new patch)
devicetree binding
- Patch 2 (single patch in v2)
Fix typos in commit log DT example.
Avoid wildcard for PWM nexus node properties in the commit log.
Patches in v3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | dt-bindings: pwm: Add support for PWM nexus nodeDocumentation/ | +65 | 1 reply | |
| 2/2 | pwm: Add support for pwm nexus dt bindingsdrivers/ | +1 | 5 replies |
Reviews trailers per patch
1 of 2 patches has a Reviewed-by or Acked-by.
| Patch | Rob Herring (Arm) |
|---|---|
| 1/2 | R-b |
| 2/2 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v3 0/2] pwm: Add support for pwm nexus node
Platforms can have a standardized connector/expansion slot that exposes PWMs signals to expansion boards.
A nexus node [1] 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.
This is particularly useful when this consumer is described in a device-tree overlay. Indeed, to have the exact same overlay reused with several base systems the overlay needs to known only about the connector is going to be applied to without any knowledge of the SoC (or the component providing the resource) available in the system.
As an example, suppose 3 PWMs connected to a connector. The connector PWM 0 and 2 comes from the PWM 1 and 3 of the pwm-controller1. The connector PWM 1 comes from the PWM 4 of the pwm-controller2. An expansion device is connected to the connector and uses the connector PMW 1.
Nexus node support in PWM allows the following description:
soc {
soc_pwm1: pwm-controller1 {
#pwm-cells = <3>;
};
soc_pwm2: pwm-controller2 {
#pwm-cells = <3>;
};
};
connector: connector {
#pwm-cells = <3>;
pwm-map = <0 0 0 &soc_pwm1 1 0 0>,
<1 0 0 &soc_pwm2 4 0 0>,
<2 0 0 &soc_pwm1 3 0 0>;
pwm-map-mask = <0xffffffff 0x0 0x0>;
pwm-map-pass-thru = <0x0 0xffffffff 0xffffffff>;
};
expansion_device {
pwms = <&connector 1 57000 0>;
};From the expansion device point of view, the PWM requested is the PWM 1 available at the connector regardless of the exact PWM wired to this connector PWM 1. Thanks to nexus node remapping described at connector node, this PWM is the PWM 4 of the pwm-controller2.
Compared to previous iteration, this v3 series mainly adds the PWM nexus node devicetree binding.
Best regards,
Hervé Codina
Changes v2 -> v3
- Patch 1 (new patch)
devicetree binding
- Patch 2 (single patch in v2)
Fix typos in commit log DT example.
Avoid wildcard for PWM nexus node properties in the commit log.
Changes v1 -> v2
v1: https://lore.kernel.org/all/[email protected]/
- Rework commit log
Herve Codina (2):
dt-bindings: pwm: Add support for PWM nexus node
pwm: Add support for pwm nexus dt bindings
.../bindings/pwm/pwm-nexus-node.yaml | 65 +++++++++++++++++++ drivers/pwm/core.c | 3 +- 2 files changed, 66 insertions(+), 2 deletions(-) create mode 100644 Documentation/devicetree/bindings/pwm/pwm-nexus-node.yaml
Signature · 1 line
2.47.1