-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This patch adds helpers to support device tree bindings for the generic PWM API. Device tree binding documentation for PWM controllers is also provided. Acked-by: Arnd Bergmann <arnd@arndb.de> Reviewed-by: Shawn Guo <shawn.guo@linaro.org> Signed-off-by: Thierry Reding <thierry.reding@avionic-design.de>
- Loading branch information
Thierry Reding
committed
Jun 15, 2012
1 parent
e05e507
commit 7299ab7
Showing
3 changed files
with
209 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
Specifying PWM information for devices | ||
====================================== | ||
|
||
1) PWM user nodes | ||
----------------- | ||
|
||
PWM users should specify a list of PWM devices that they want to use | ||
with a property containing a 'pwm-list': | ||
|
||
pwm-list ::= <single-pwm> [pwm-list] | ||
single-pwm ::= <pwm-phandle> <pwm-specifier> | ||
pwm-phandle : phandle to PWM controller node | ||
pwm-specifier : array of #pwm-cells specifying the given PWM | ||
(controller specific) | ||
|
||
PWM properties should be named "pwms". The exact meaning of each pwms | ||
property must be documented in the device tree binding for each device. | ||
An optional property "pwm-names" may contain a list of strings to label | ||
each of the PWM devices listed in the "pwms" property. If no "pwm-names" | ||
property is given, the name of the user node will be used as fallback. | ||
|
||
Drivers for devices that use more than a single PWM device can use the | ||
"pwm-names" property to map the name of the PWM device requested by the | ||
pwm_get() call to an index into the list given by the "pwms" property. | ||
|
||
The following example could be used to describe a PWM-based backlight | ||
device: | ||
|
||
pwm: pwm { | ||
#pwm-cells = <2>; | ||
}; | ||
|
||
[...] | ||
|
||
bl: backlight { | ||
pwms = <&pwm 0 5000000>; | ||
pwm-names = "backlight"; | ||
}; | ||
|
||
pwm-specifier typically encodes the chip-relative PWM number and the PWM | ||
period in nanoseconds. Note that in the example above, specifying the | ||
"pwm-names" is redundant because the name "backlight" would be used as | ||
fallback anyway. | ||
|
||
2) PWM controller nodes | ||
----------------------- | ||
|
||
PWM controller nodes must specify the number of cells used for the | ||
specifier using the '#pwm-cells' property. | ||
|
||
An example PWM controller might look like this: | ||
|
||
pwm: pwm@7000a000 { | ||
compatible = "nvidia,tegra20-pwm"; | ||
reg = <0x7000a000 0x100>; | ||
#pwm-cells = <2>; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters