diff options
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/devicetree/bindings/pwm/bcm-kona-pwm.txt | 21 | ||||
| -rw-r--r-- | Documentation/pwm.txt | 10 |
2 files changed, 30 insertions, 1 deletions
diff --git a/Documentation/devicetree/bindings/pwm/bcm-kona-pwm.txt b/Documentation/devicetree/bindings/pwm/bcm-kona-pwm.txt new file mode 100644 index 000000000000..8eae9fe7841c --- /dev/null +++ b/Documentation/devicetree/bindings/pwm/bcm-kona-pwm.txt | |||
| @@ -0,0 +1,21 @@ | |||
| 1 | Broadcom Kona PWM controller device tree bindings | ||
| 2 | |||
| 3 | This controller has 6 channels. | ||
| 4 | |||
| 5 | Required Properties : | ||
| 6 | - compatible: should contain "brcm,kona-pwm" | ||
| 7 | - reg: physical base address and length of the controller's registers | ||
| 8 | - clocks: phandle + clock specifier pair for the external clock | ||
| 9 | - #pwm-cells: Should be 3. See pwm.txt in this directory for a | ||
| 10 | description of the cells format. | ||
| 11 | |||
| 12 | Refer to clocks/clock-bindings.txt for generic clock consumer properties. | ||
| 13 | |||
| 14 | Example: | ||
| 15 | |||
| 16 | pwm: pwm@3e01a000 { | ||
| 17 | compatible = "brcm,bcm11351-pwm", "brcm,kona-pwm"; | ||
| 18 | reg = <0x3e01a000 0xc4>; | ||
| 19 | clocks = <&pwm_clk>; | ||
| 20 | #pwm-cells = <3>; | ||
| 21 | }; | ||
diff --git a/Documentation/pwm.txt b/Documentation/pwm.txt index 93cb97974986..ca895fd211e4 100644 --- a/Documentation/pwm.txt +++ b/Documentation/pwm.txt | |||
| @@ -19,7 +19,8 @@ should instead register a static mapping that can be used to match PWM | |||
| 19 | consumers to providers, as given in the following example: | 19 | consumers to providers, as given in the following example: |
| 20 | 20 | ||
| 21 | static struct pwm_lookup board_pwm_lookup[] = { | 21 | static struct pwm_lookup board_pwm_lookup[] = { |
| 22 | PWM_LOOKUP("tegra-pwm", 0, "pwm-backlight", NULL), | 22 | PWM_LOOKUP("tegra-pwm", 0, "pwm-backlight", NULL, |
| 23 | 50000, PWM_POLARITY_NORMAL), | ||
| 23 | }; | 24 | }; |
| 24 | 25 | ||
| 25 | static void __init board_init(void) | 26 | static void __init board_init(void) |
| @@ -97,6 +98,13 @@ pwm_chip as argument which provides a description of the PWM chip, the | |||
| 97 | number of PWM devices provided by the chip and the chip-specific | 98 | number of PWM devices provided by the chip and the chip-specific |
| 98 | implementation of the supported PWM operations to the framework. | 99 | implementation of the supported PWM operations to the framework. |
| 99 | 100 | ||
| 101 | When implementing polarity support in a PWM driver, make sure to respect the | ||
| 102 | signal conventions in the PWM framework. By definition, normal polarity | ||
| 103 | characterizes a signal starts high for the duration of the duty cycle and | ||
| 104 | goes low for the remainder of the period. Conversely, a signal with inversed | ||
| 105 | polarity starts low for the duration of the duty cycle and goes high for the | ||
| 106 | remainder of the period. | ||
| 107 | |||
| 100 | Locking | 108 | Locking |
| 101 | ------- | 109 | ------- |
| 102 | 110 | ||
