Home
last modified time | relevance | path

Searched refs:PWM (Results 1 – 25 of 206) sorted by relevance

123456789

/Linux-v4.19/drivers/pwm/
DKconfig1 menuconfig PWM config
2 bool "Pulse-Width Modulation (PWM) Support"
4 Generic Pulse-Width Modulation (PWM) support.
13 This framework provides a generic interface to PWM devices
15 to register and unregister a PWM chip, an abstraction of a PWM
16 controller, that supports one or more PWM devices. Client
17 drivers can request PWM devices and use the generic framework
20 This generic framework replaces the legacy PWM framework which
29 if PWM
36 tristate "AB8500 PWM support"
[all …]
/Linux-v4.19/Documentation/
Dpwm.txt2 Pulse Width Modulation (PWM) interface
5 This provides an overview about the Linux PWM interface
9 the Linux PWM API (although they could). However, PWMs are often
12 this kind of flexibility the generic PWM API exists.
17 Users of the legacy PWM API use unique IDs to refer to PWM devices.
19 Instead of referring to a PWM device via its unique ID, board setup code
20 should instead register a static mapping that can be used to match PWM
38 Legacy users can request a PWM device using pwm_request() and free it
42 device or a consumer name. pwm_put() is used to free the PWM device. Managed
45 After being requested, a PWM has to be configured using::
[all …]
/Linux-v4.19/Documentation/devicetree/bindings/pwm/
Dpwm.txt1 Specifying PWM information for devices
4 1) PWM user nodes
7 PWM users should specify a list of PWM devices that they want to use
12 pwm-phandle : phandle to PWM controller node
13 pwm-specifier : array of #pwm-cells specifying the given PWM
16 PWM properties should be named "pwms". The exact meaning of each pwms
19 each of the PWM devices listed in the "pwms" property. If no "pwm-names"
22 Drivers for devices that use more than a single PWM device can use the
23 "pwm-names" property to map the name of the PWM device requested by the
26 The following example could be used to describe a PWM-based backlight
[all …]
Drenesas,tpu-pwm.txt1 * Renesas R-Car Timer Pulse Unit PWM Controller
6 - "renesas,tpu-r8a73a4": for R8A73A4 (R-Mobile APE6) compatible PWM controller.
7 - "renesas,tpu-r8a7740": for R8A7740 (R-Mobile A1) compatible PWM controller.
8 - "renesas,tpu-r8a7743": for R8A7743 (RZ/G1M) compatible PWM controller.
9 - "renesas,tpu-r8a7745": for R8A7745 (RZ/G1E) compatible PWM controller.
10 - "renesas,tpu-r8a7790": for R8A7790 (R-Car H2) compatible PWM controller.
11 - "renesas,tpu": for generic R-Car and RZ/G1 TPU PWM controller.
13 - reg: Base address and length of each memory resource used by the PWM
20 Please refer to pwm.txt in this directory for details of the common PWM bindings
Dpwm-lp3943.txt1 TI/National Semiconductor LP3943 PWM controller
9 - ti,pwm0 or ti,pwm1: Output pin number(s) for PWM channel 0 or 1.
17 PWM 0 is for RGB LED brightness control
18 PWM 1 is for brightness control of LP8557 backlight device
26 * PWM 0 : output 8, 9 and 10
27 * PWM 1 : output 15
39 /* LEDs control with PWM 0 of LP3943 */
50 /* Backlight control with PWM 1 of LP3943 */
Dpwm-samsung.txt1 * Samsung PWM timers
3 Samsung SoCs contain PWM timer blocks which can be used for system clock source
4 and clock event timers, as well as to drive SoC outputs with PWM signal. Each
5 PWM timer block provides 5 PWM channels (not all of them can drive physical
23 - "timers" - PWM base clock used to generate PWM signals,
25 - "pwm-tclk0" - first external PWM clock source,
26 - "pwm-tclk1" - second external PWM clock source.
37 - samsung,pwm-outputs: list of PWM channels used as PWM outputs on particular
38 platform - an array of up to 5 elements being indices of PWM channels
Dpxa-pwm.txt1 Marvell PWM controller
9 - reg: Physical base address and length of the registers used by the PWM channel
10 Note that one device instance must be created for each PWM that is used, so the
11 length covers only the register window for one PWM output, not that of the
12 entire PWM controller. Currently length is 0x10 for all supported devices.
16 Example PWM device node:
24 Example PWM client node:
Dgoogle,cros-ec-pwm.txt1 * PWM controlled by ChromeOS EC
3 Google's ChromeOS EC PWM is a simple PWM attached to the Embedded Controller
6 An EC PWM node should be only found as a sub-node of the EC node (see
11 - #pwm-cells: Should be 1. The cell specifies the PWM index.
Dpwm-st.txt1 STMicroelectronics PWM driver bindings
6 - #pwm-cells : Number of cells used to specify a PWM. First cell
7 specifies the per-chip index of the PWM to use and the
14 for PWM module.
17 - clocks: phandle of the clock used by the PWM module.
22 - st,pwm-num-chan: Number of available PWM channels. Default is 0.
Dpwm-mediatek.txt1 MediaTek PWM controller
12 - clocks: phandle and clock specifier of the PWM reference clock.
16 - "main": clock used by the PWM core
17 - "pwm1-8": the eight per PWM clocks for mt2712
18 - "pwm1-6": the six per PWM clocks for mt7622
19 - "pwm1-5": the five per PWM clocks for mt7623
/Linux-v4.19/Documentation/ABI/testing/
Dsysfs-class-pwm6 The pwm/ class sub-directory belongs to the Generic PWM
7 Framework and provides a sysfs interface for using PWM
16 probed PWM controller/chip where N is the base of the
17 PWM chip.
24 The number of PWM channels supported by the PWM chip.
31 Exports a PWM channel from the PWM chip for sysfs control.
39 Unexports a PWM channel.
47 each exported PWM channel where X is the exported PWM
55 Sets the PWM signal period in nanoseconds.
62 Sets the PWM signal duty cycle in nanoseconds.
[all …]
Dsysfs-class-backlight-driver-lm353341 Set the PWM-input control mask (5 bits), where
43 bit 5 - PWM-input enabled in Zone 4
44 bit 4 - PWM-input enabled in Zone 3
45 bit 3 - PWM-input enabled in Zone 2
46 bit 2 - PWM-input enabled in Zone 1
47 bit 1 - PWM-input enabled in Zone 0
48 bit 0 - PWM-input enabled
Dsysfs-class-led-driver-lm353358 Set the PWM-input control mask (5 bits), where
60 bit 5 - PWM-input enabled in Zone 4
61 bit 4 - PWM-input enabled in Zone 3
62 bit 3 - PWM-input enabled in Zone 2
63 bit 2 - PWM-input enabled in Zone 1
64 bit 1 - PWM-input enabled in Zone 0
65 bit 0 - PWM-input enabled
/Linux-v4.19/arch/mips/loongson32/
DKconfig41 bool "Use PWM Timer for clockevent/clocksource"
45 This option changes the default clockevent/clocksource to PWM Timer,
56 bool "Use PWM Timer 0"
58 Use PWM Timer 0 as the default clockevent/clocksourcer.
61 bool "Use PWM Timer 1"
63 Use PWM Timer 1 as the default clockevent/clocksourcer.
66 bool "Use PWM Timer 2"
68 Use PWM Timer 2 as the default clockevent/clocksourcer.
71 bool "Use PWM Timer 3"
73 Use PWM Timer 3 as the default clockevent/clocksourcer.
/Linux-v4.19/Documentation/devicetree/bindings/hwmon/
Daspeed-pwm-tacho.txt1 ASPEED AST2400/AST2500 PWM and Fan Tacho controller device driver
3 The ASPEED PWM controller can support upto 8 PWM outputs. The ASPEED Fan Tacho
6 There can be upto 8 fans supported. Each fan can have one PWM output and
20 - pinctrl-0 : phandle referencing pin configuration of the PWM ports.
32 representing a fan. If there are 8 fans each fan can have one PWM port and
34 For PWM port can be configured cooling-levels to create cooling device.
38 - reg : should specify PWM source port.
39 integer value in the range 0 to 7 with 0 indicating PWM port A and
40 7 indicating PWM port H.
42 - cooling-levels: PWM duty cycle values in a range from 0 to 255
Dnpcm750-pwm-fan.txt1 Nuvoton NPCM7xx PWM and Fan Tacho controller device
3 The Nuvoton BMC NPCM7XX supports 8 Pulse-width modulation (PWM)
12 * "pwm" for the PWM registers.
16 * "pwm" for PWM controller operating clock.
20 - pinctrl-0 : phandle referencing pin configuration of the PWM and Fan
26 Each fan subnode must have one PWM channel and atleast one Fan tach channel.
28 For PWM channel can be configured cooling-levels to create cooling device.
32 - reg : specify the PWM output channel.
34 the PWM channel number that used.
43 - cooling-levels: PWM duty cycle values in a range from 0 to 255
/Linux-v4.19/Documentation/hwmon/
Dadt747543 for measuring fan speed. There are three (3) PWM outputs that can be used
46 A sophisticated control system for the PWM outputs is designed into the
48 three temperature sensors. Each PWM output is individually adjustable and
49 programmable. Once configured, the ADT747x will adjust the PWM outputs in
51 This feature can also be disabled for manual control of the PWM's.
91 an optimal configuration for the automatic PWM control.
96 The driver exposes two trip points per PWM channel.
98 point1: Set the PWM speed at the lower temperature bound
99 point2: Set the PWM speed at the higher temperature bound
101 The ADT747x will scale the PWM linearly between the lower and higher PWM
[all …]
Dpwm-fan4 This driver enables the use of a PWM module to drive a fan. It uses the
5 generic PWM interface thus it is hardware independent. It can be used on
6 many SoCs, as long as the SoC supplies a PWM line driver that exposes
7 the generic PWM API.
15 a PWM output. It uses the generic PWM interface, thus it can be used with
Ddme173730 and PWM output control functions. Using this parameter
47 up to 5 PWM outputs pwm[1-3,5-6] for controlling fan speeds both manually and
147 PWM Output Control
150 This chip features 5 PWM outputs. PWM outputs 1-3 are associated with fan
151 inputs 1-3 and PWM outputs 5-6 are associated with fan inputs 5-6. PWM outputs
153 the appropriate enable attribute accordingly. PWM outputs 5-6 can only operate
156 appropriate PWM attribute. In automatic mode, the PWM attribute returns the
157 current duty-cycle as set by the fan controller in the chip. All PWM outputs
160 In automatic mode, the chip supports the setting of the PWM ramp rate which
161 defines how fast the PWM output is adjusting to changes of the associated
[all …]
Dadt747021 There are four (4) PWM outputs that can be used to control fan speed.
23 A sophisticated control system for the PWM outputs is designed into the ADT7470
25 temperature sensors. Each PWM output is individually adjustable and
26 programmable. Once configured, the ADT7470 will adjust the PWM outputs in
28 feature can also be disabled for manual control of the PWM's.
47 determining an optimal configuration for the automatic PWM control.
54 * PWM Control
63 the temperature is between the two temperature boundaries. PWM values range
65 temperature sensor associated with the PWM control exceeds
68 The driver also allows control of the PWM frequency:
[all …]
Dw8379337 6 remote temperatures, up to 8 sets of PWM fan controls, SmartFan
38 (automatic fan speed control) on all temperature/PWM combinations, 2
66 * SmartFan/PWM control
73 Each temperature channel can control all the 8 PWM outputs (by setting the
78 PWM value requests from different temperature channels, but the chip
79 will always pick the safest (max) PWM value for each fan.
83 thermal_cruiseX + toleranceX, the chip will increase the PWM value,
85 the PWM value. If the temperature is within the tolerance range, the PWM
88 SmartFanII works differently, you have to define up to 7 PWM, temperature
89 trip points, defining a PWM/temperature curve which the chip will follow.
[all …]
/Linux-v4.19/Documentation/driver-api/
Dmiscellaneous.rst25 Pulse-Width Modulation (PWM)
31 The PWM framework provides an abstraction for providers and consumers of
32 PWM signals. A controller that provides one or more PWM signals is
37 A chip exposes one or more PWM signal sources, each of which exposed as
39 performed on PWM devices to control the period, duty cycle, polarity and
42 Note that PWM devices are exclusive resources: they can always only be
/Linux-v4.19/Documentation/devicetree/bindings/clock/
Dpwm-clock.txt1 Binding for an external clock signal driven by a PWM pin.
3 This binding uses the common clock binding[1] and the common PWM binding[2].
11 - pwms : from common PWM binding; this determines the clock frequency
12 via the period given in the PWM specifier.
16 - clock-frequency : Exact output frequency, in case the PWM period
/Linux-v4.19/Documentation/devicetree/bindings/leds/
Dleds-pwm.txt1 LED connected to PWM
10 - pwms : PWM property to point to the PWM device (phandle)/port (id) and to
12 - pwm-names : (optional) Name to be used by the PWM subsystem for the PWM device
32 /* provides one PWM (id 0 for Charing indicator LED) */
/Linux-v4.19/Documentation/devicetree/bindings/leds/backlight/
Dpwm-backlight.txt5 - pwms: OF device-tree PWM specification (see PWM binding[0])
9 - pwm-names: a list of names for the PWM devices specified in the
10 "pwms" property (see PWM binding[0])
13 - post-pwm-on-delay-ms: Delay in ms between setting an initial (non-zero) PWM
16 and setting PWM value to 0.
19 0 will do. The actual brightness level (PWM duty cycle)

123456789