| /linux/drivers/pwm/ |
| H A D | Kconfig | 2 menuconfig PWM config
3 bool "Pulse-Width Modulation (PWM) Support"
5 Generic Pulse-Width Modulation (PWM) support.
14 This framework provides a generic interface to PWM devices
16 to register and unregister a PWM chip, an abstraction of a PWM
17 controller, that supports one or more PWM devices. Client
18 drivers can request PWM devices and use the generic framework
21 This generic framework replaces the legacy PWM framework which
30 if PWM
33 bool "PWM lowlevel drivers additional checks and debug messages"
[all …]
|
| /linux/Documentation/driver-api/ |
| H A D | pwm.rst | 2 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
39 consumer name. pwm_put() is used to free the PWM device. Managed variants of
42 After being requested, a PWM has to be configured using::
46 This API controls both the PWM period/duty_cycle config and the
[all …]
|
| H A D | miscellaneous.rst | 24 Pulse-Width Modulation (PWM)
30 The PWM framework provides an abstraction for providers and consumers of
31 PWM signals. A controller that provides one or more PWM signals is
36 A chip exposes one or more PWM signal sources, each of which exposed as
38 performed on PWM devices to control the period, duty cycle, polarity and
41 Note that PWM devices are exclusive resources: they can always only be
|
| /linux/Documentation/devicetree/bindings/pwm/ |
| H A D | pwm.txt | 1 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 …]
|
| H A D | pwm-lp3943.txt | 1 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 */
|
| H A D | pwm-sprd.txt | 1 Spreadtrum PWM controller
3 Spreadtrum SoCs PWM controller provides 4 PWM channels.
10 "pwmn": used to derive the functional clock for PWM channel n (n range: 0 ~ 3).
11 "enablen": for PWM channel n enable clock (n range: 0 ~ 3).
16 - assigned-clocks: Reference to the PWM clock entries.
17 - assigned-clock-parents: The phandle of the parent clock of PWM clock.
|
| H A D | pwm-st.txt | 1 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.
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-pwm | 6 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 …]
|
| H A D | sysfs-class-backlight-driver-lm3533 | 45 Set the PWM-input control mask (5 bits), where:
48 bit 5 PWM-input enabled in Zone 4
49 bit 4 PWM-input enabled in Zone 3
50 bit 3 PWM-input enabled in Zone 2
51 bit 2 PWM-input enabled in Zone 1
52 bit 1 PWM-input enabled in Zone 0
53 bit 0 PWM-input enabled
|
| H A D | sysfs-class-led-driver-lm3533 | 64 Set the PWM-input control mask (5 bits), where:
67 bit 5 PWM-input enabled in Zone 4
68 bit 4 PWM-input enabled in Zone 3
69 bit 3 PWM-input enabled in Zone 2
70 bit 2 PWM-input enabled in Zone 1
71 bit 1 PWM-input enabled in Zone 0
72 bit 0 PWM-input enabled
|
| /linux/Documentation/devicetree/bindings/hwmon/ |
| H A D | aspeed-pwm-tacho.txt | 1 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
|
| H A D | npcm750-pwm-fan.txt | 1 Nuvoton NPCM PWM and Fan Tacho controller device
3 The Nuvoton BMC NPCM7XX supports 8 Pulse-width modulation (PWM)
6 The Nuvoton BMC NPCM8XX supports 12 Pulse-width modulation (PWM)
16 * "pwm" for the PWM registers.
20 * "pwm" for PWM controller operating clock.
24 - pinctrl-0 : phandle referencing pin configuration of the PWM and Fan
30 Each fan subnode must have one PWM channel and at least one Fan tach channel.
32 For PWM channel can be configured cooling-levels to create cooling device.
36 - reg : specify the PWM output channel.
38 the PWM channel number that used.
[all …]
|
| /linux/Documentation/hwmon/ |
| H A D | adt7475.rst | 59 for measuring fan speed. There are three (3) PWM outputs that can be used
62 A sophisticated control system for the PWM outputs is designed into the
64 three temperature sensors. Each PWM output is individually adjustable and
65 programmable. Once configured, the ADT747x will adjust the PWM outputs in
67 This feature can also be disabled for manual control of the PWM's.
122 an optimal configuration for the automatic PWM control.
127 The driver exposes two trip points per PWM channel.
129 - point1: Set the PWM speed at the lower temperature bound
130 - point2: Set the PWM speed at the higher temperature bound
132 The ADT747x will scale the PWM linearly between the lower and higher PWM
[all …]
|
| H A D | dme1737.rst | 47 and PWM output control functions. Using this parameter
66 up to 5 PWM outputs pwm[1-3,5-6] for controlling fan speeds both manually and
170 PWM Output Control
173 This chip features 5 PWM outputs. PWM outputs 1-3 are associated with fan
174 inputs 1-3 and PWM outputs 5-6 are associated with fan inputs 5-6. PWM outputs
176 the appropriate enable attribute accordingly. PWM outputs 5-6 can only operate
179 appropriate PWM attribute. In automatic mode, the PWM attribute returns the
180 current duty-cycle as set by the fan controller in the chip. All PWM outputs
183 In automatic mode, the chip supports the setting of the PWM ramp rate which
184 defines how fast the PWM output is adjusting to changes of the associated
[all …]
|
| H A D | adt7470.rst | 25 There are four (4) PWM outputs that can be used to control fan speed.
27 A sophisticated control system for the PWM outputs is designed into the ADT7470
29 temperature sensors. Each PWM output is individually adjustable and
30 programmable. Once configured, the ADT7470 will adjust the PWM outputs in
32 feature can also be disabled for manual control of the PWM's.
51 determining an optimal configuration for the automatic PWM control.
58 * PWM Control
67 the temperature is between the two temperature boundaries. PWM values range
69 temperature sensor associated with the PWM control exceeds
72 The driver also allows control of the PWM frequency:
[all …]
|
| H A D | max31760.rst | 21 The MAX31760 integrates temperature sensing along with precision PWM fan
29 user-programmed PWM values. The flexible LUT-based architecture enables
49 1 PWM value for T < +18°C
50 2 PWM value for +18°C ≤ T < +20°C
51 3 PWM value for +20°C ≤ T < +22°C
53 47 PWM value for +108°C ≤ T < +110°C
54 48 PWM value for T ≥ +110°C
71 pwm1 PWM value for direct fan control
73 pwm1_freq PWM frequency in hertz
75 pwm1_auto_point[1-48]_pwm PWM value for LUT point
|
| H A D | lm85.rst | 96 VID signals from the processor to the VRM. Lastly, there are three (3) PWM
110 A sophisticated control system for the PWM outputs is designed into the
112 three temperature sensors. Each PWM output is individually adjustable and
113 programmable. Once configured, the LM85 will adjust the PWM outputs in
115 This feature can also be disabled for manual control of the PWM's.
130 Both have special circuitry to compensate for PWM interactions with the
152 The ADT7468 has a high-frequency PWM mode, where all PWM outputs are
153 driven by a 22.5 kHz clock. This is a global mode, not per-PWM output,
154 which means that setting any PWM frequency above 11.3 kHz will switch
155 all 3 PWM outputs to a 22.5 kHz frequency. Conversely, setting any PWM
[all …]
|
| H A D | w83793.rst | 42 6 remote temperatures, up to 8 sets of PWM fan controls, SmartFan
43 (automatic fan speed control) on all temperature/PWM combinations, 2
73 * SmartFan/PWM control
80 Each temperature channel can control all the 8 PWM outputs (by setting the
85 PWM value requests from different temperature channels, but the chip
86 will always pick the safest (max) PWM value for each fan.
90 thermal_cruiseX + toleranceX, the chip will increase the PWM value,
92 the PWM value. If the temperature is within the tolerance range, the PWM
95 SmartFanII works differently, you have to define up to 7 PWM, temperature
96 trip points, defining a PWM/temperature curve which the chip will follow.
[all …]
|
| H A D | pwm-fan.rst | 4 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
|
| H A D | nzxt-kraken3.rst | 24 All models expose liquid temperature and pump speed (in RPM), as well as PWM
25 control (either as a fixed value or through a temp-PWM curve). The Z-series and
27 fan, with the same PWM control capabilities.
30 for the manual control mode and 2 is for the liquid temp to PWM curve mode.
35 the detected liquid temperature. Only PWM values (ranging from 0-255) can be set.
61 1 Direct PWM mode (applies value in corresponding PWM entry)
62 2 Curve control mode (applies the temp-PWM duty curve based on coolant temp)
76 temp[1-2]_auto_point[1-40]_pwm Temp-PWM duty curves (for pump and fan), related to coolant temp
|
| H A D | adt7462.rst | 27 A sophisticated control system for the PWM outputs is designed into the ADT7462
29 temperature sensors. Each PWM output is individually adjustable and
30 programmable. Once configured, the ADT7462 will adjust the PWM outputs in
32 feature can also be disabled for manual control of the PWM's.
49 determining an optimal configuration for the automatic PWM control.
59 * PWM Control
68 the temperature is between the two temperature boundaries. PWM values range
70 temperature sensor associated with the PWM control exceeds temp#_max.
|
| H A D | lm93.rst | 61 voltages. To set fan speed, the LM93 has two PWM outputs that are each
107 The LM93 can also override the #PROCHOT pins by driving a PWM signal onto
115 contains a value controlling the duty cycle for the PWM signal used when
129 If a fan is driven using a low-side drive PWM, the tachometer
138 enabled if the PWM output frequency is 22500 Hz (see below).
140 Manual PWM
143 The LM93 has a fixed or override mode for the two PWM outputs (although, there
152 PWM mode is disabled, the value of pwm1 and pwm2 indicates the current duty
155 PWM Output Frequency
158 The LM93 supports several different frequencies for the PWM output channels.
[all …]
|
| /linux/Documentation/devicetree/bindings/clock/ |
| H A D | nvidia,tegra124-dfll.txt | 10 communicating with an off-chip PMIC either via an I2C bus or via PWM signals.
50 - nvidia,pwm-to-pmic: Use PWM to control regulator rather then I2C.
55 Required properties for PWM mode:
56 - nvidia,pwm-period-nanoseconds: period of PWM square wave in nanoseconds.
57 - nvidia,pwm-tristate-microvolts: Regulator voltage in micro volts when PWM
58 control is disabled and the PWM output is tristated. Note that this voltage is
60 - nvidia,pwm-min-microvolts: Regulator voltage in micro volts when PWM control
61 is enabled and PWM output is low. Hence, this is the minimum output voltage
62 that the regulator supports when PWM control is enabled.
67 - pinctrl-0: I/O pad configuration when PWM control is enabled.
[all …]
|
| /linux/arch/arm/boot/dts/nxp/imx/ |
| H A D | imx7-colibri-eval-v3.dtsi | 21 * The Atmel maxtouch controller uses SODIMM 28/30, also used for PWM<B>, PWM<C>, aka pwm2, pwm3.
60 /* Colibri PWM<A> */
65 /* Colibri PWM<B> */
71 /* Colibri PWM<C> */
77 /* Colibri PWM<D> */
|
| H A D | imx7-colibri-iris.dtsi | 12 * The Atmel maxtouch controller uses SODIMM 28/30, also used for PWM<B>, PWM<C>, aka pwm2, pwm3.
58 /* Colibri PWM<A> */
63 /* Colibri PWM<B> */
69 /* Colibri PWM<C> */
75 /* Colibri PWM<D> */
|