Home
last modified time | relevance | path

Searched +full:pwm +full:- +full:number (Results 1 – 25 of 225) sorted by relevance

123456789

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/pwm/
Dmxs-pwm.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pwm/mxs-pwm.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Freescale MXS PWM controller
10 - Shawn Guo <shawnguo@kernel.org>
11 - Anson Huang <anson.huang@nxp.com>
16 - fsl,imx23-pwm
21 "#pwm-cells":
24 fsl,pwm-number:
[all …]
Dpwm-st.txt1 STMicroelectronics PWM driver bindings
2 --------------------------------------
5 - compatible : "st,pwm"
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
8 second cell is the period in nanoseconds - fixed to 2
10 - reg : Physical base address and length of the controller's
12 - pinctrl-names: Set to "default".
13 - pinctrl-0: List of phandles pointing to pin configuration nodes
14 for PWM module.
[all …]
Dpwm.txt1 Specifying PWM information for devices
4 1) PWM user nodes
5 -----------------
7 PWM users should specify a list of PWM devices that they want to use
8 with a property containing a 'pwm-list':
10 pwm-list ::= <single-pwm> [pwm-list]
11 single-pwm ::= <pwm-phandle> <pwm-specifier>
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
[all …]
Dpwm.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/pwm/pwm.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: PWM controllers (providers)
10 - Thierry Reding <thierry.reding@gmail.com>
14 pattern: "^pwm(@.*|-[0-9a-f])*$"
16 "#pwm-cells":
18 Number of cells in a PWM specifier.
21 - "#pwm-cells"
[all …]
Dpwm-lp3943.txt1 TI/National Semiconductor LP3943 PWM controller
4 - compatible: "ti,lp3943-pwm"
5 - #pwm-cells: Should be 2. See pwm.yaml in this directory for a
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
29 pwm3943: pwm {
30 compatible = "ti,lp3943-pwm";
[all …]
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-class-pwm1 What: /sys/class/pwm/
6 The pwm/ class sub-directory belongs to the Generic PWM
7 Framework and provides a sysfs interface for using PWM
10 What: /sys/class/pwm/pwmchipN/
15 A /sys/class/pwm/pwmchipN directory is created for each
16 probed PWM controller/chip where N is the base of the
17 PWM chip.
19 What: /sys/class/pwm/pwmchipN/npwm
24 The number of PWM channels supported by the PWM chip.
26 What: /sys/class/pwm/pwmchipN/export
[all …]
/kernel/linux/linux-5.10/Documentation/driver-api/
Dpwm.rst2 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.
15 ----------------
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
24 PWM_LOOKUP("tegra-pwm", 0, "pwm-backlight", NULL,
36 ----------
[all …]
/kernel/linux/linux-5.10/drivers/video/backlight/
Dpwm_bl.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Simple PWM based backlight control, board code has to setup
4 * 1) pin configuration so PWM waveforms can output
17 #include <linux/pwm.h>
23 struct pwm_device *pwm; member
47 pwm_get_state(pb->pwm, &state); in pwm_backlight_power_on()
48 if (pb->enabled) in pwm_backlight_power_on()
51 err = regulator_enable(pb->power_supply); in pwm_backlight_power_on()
53 dev_err(pb->dev, "failed to enable power supply\n"); in pwm_backlight_power_on()
56 pwm_apply_state(pb->pwm, &state); in pwm_backlight_power_on()
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/hwmon/
Dnpcm750-pwm-fan.txt1 Nuvoton NPCM7xx PWM and Fan Tacho controller device
3 The Nuvoton BMC NPCM7XX supports 8 Pulse-width modulation (PWM)
6 Required properties for pwm-fan node
7 - #address-cells : should be 1.
8 - #size-cells : should be 0.
9 - compatible : "nuvoton,npcm750-pwm-fan" for Poleg NPCM7XX.
10 - reg : specifies physical base address and size of the registers.
11 - reg-names : must contain:
12 * "pwm" for the PWM registers.
14 - clocks : phandle of reference clocks.
[all …]
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
9 Required properties for pwm-tacho node:
10 - #address-cells : should be 1.
12 - #size-cells : should be 1.
14 - #cooling-cells: should be 2.
16 - reg : address and length of the register set for the device.
18 - pinctrl-names : a pinctrl state named "default" must be defined.
20 - pinctrl-0 : phandle referencing pin configuration of the PWM ports.
[all …]
Dpwm-fan.txt1 Bindings for a fan connected to the PWM lines
4 - compatible : "pwm-fan"
5 - pwms : the PWM that is used to control the PWM fan
6 - cooling-levels : PWM duty cycle values in a range from 0 to 255
10 - fan-supply : phandle to the regulator that provides power to the fan
11 - interrupts : This contains a single interrupt specifier which
14 defined number of interrupts per fan revolution, which
16 See interrupt-controller/interrupts.txt for the format.
17 - pulses-per-revolution : define the tachometer pulses per fan revolution as
22 fan0: pwm-fan {
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/gpio/
Dgpio-mvebu.txt5 - compatible : Should be "marvell,orion-gpio", "marvell,mv78200-gpio",
6 "marvell,armadaxp-gpio" or "marvell,armada-8k-gpio".
8 "marvell,orion-gpio" should be used for Orion, Kirkwood, Dove,
9 Discovery (except MV78200) and Armada 370. "marvell,mv78200-gpio"
12 "marvel,armadaxp-gpio" should be used for all Armada XP SoCs
15 "marvell,armada-8k-gpio" should be used for the Armada 7K and 8K
17 Documentation/devicetree/bindings/arm/marvell/ap80x-system-controller.txt
20 - reg: Address and length of the register set for the device. Only one
21 entry is expected, except for the "marvell,armadaxp-gpio" variant
23 one for the per-cpu registers. Not used for marvell,armada-8k-gpio.
[all …]
/kernel/linux/linux-5.10/Documentation/hwmon/
Dsysfs-interface.rst5 through the sysfs interface. Since lm-sensors 3.0.0, libsensors is
6 completely chip-independent. It assumes that all the kernel drivers
10 This is a major improvement compared to lm-sensors 2.
22 For this reason, even if we aim at a chip-independent libsensors, it will
37 Up to lm-sensors 3.0.0, libsensors looks for hardware monitoring attributes
38 in the "physical" device directory. Since lm-sensors 3.0.1, attributes found
47 The common scheme for files naming is: <type><number>_<item>. Usual
52 this). A number is always used for elements that can be present more
55 they have a simple name, and no number.
61 to cause an alarm) is chip-dependent.
[all …]
Df71882fg.rst103 This is the 64-pin variant of the F71889FG, they have the
119 -----------
125 These chips also have fan controlling features, using either DC or PWM, in
133 ----------
136 interface as documented in sysfs-interface, without any exceptions.
140 -----------
142 Both PWM (pulse-width modulation) and DC fan speed control methods are
149 vica versa. So the temperature zone trip points 1-4 (or 1-2) go from high temp
153 There are 2 modes to specify the speed of the fan, PWM duty cycle (or DC
154 voltage) mode, where 0-100% duty cycle (0-100% of 12V) is specified. And RPM
[all …]
Ddme1737.rst18 Addresses scanned: none, address read from Super-I/O config space
34 Addresses scanned: none, address read from Super-I/O config space
43 -----------------
47 and PWM output control functions. Using this parameter
52 Include non-standard LPC addresses 0x162e and 0x164e
55 - VIA EPIA SN18000
59 -----------
63 and SCH5127 Super-I/O chips. These chips feature monitoring of 3 temp sensors
64 temp[1-3] (2 remote diodes and 1 internal), 8 voltages in[0-7] (7 external and
65 1 internal) and up to 6 fan speeds fan[1-6]. Additionally, the chips implement
[all …]
Dg762.rst4 The GMT G762 Fan Speed PWM Controller is connected directly to a fan
5 and performs closed-loop or open-loop control of the fan speed. Two
6 modes - PWM or DC - are supported by the device.
9 http://natisbad.org/NAS/ref/GMT_EDS-762_763-080710-0.2.pdf. sysfs
10 bindings are described in Documentation/hwmon/sysfs-interface.rst.
25 set desired fan speed. This only makes sense in closed-loop
36 number of pulses per fan revolution. Supported values
44 in closed-loop control mode, if fan RPM value is 25% out
50 speed control (open-loop) via pwm1 described below, 2 for
51 automatic fan speed control (closed-loop) via fan1_target
[all …]
/kernel/linux/linux-5.10/drivers/pwm/
Dpwm-mxs.c1 // SPDX-License-Identifier: GPL-2.0+
13 #include <linux/pwm.h>
47 static int mxs_pwm_apply(struct pwm_chip *chip, struct pwm_device *pwm, in mxs_pwm_apply() argument
58 * If the PWM channel is disabled, make sure to turn on the in mxs_pwm_apply()
62 if (!pwm_is_enabled(pwm)) { in mxs_pwm_apply()
63 ret = clk_prepare_enable(mxs->clk); in mxs_pwm_apply()
68 if (!state->enabled && pwm_is_enabled(pwm)) in mxs_pwm_apply()
69 writel(1 << pwm->hwpwm, mxs->base + PWM_CTRL + CLR); in mxs_pwm_apply()
71 rate = clk_get_rate(mxs->clk); in mxs_pwm_apply()
74 c = c * state->period; in mxs_pwm_apply()
[all …]
Dpwm-cros-ec.c1 // SPDX-License-Identifier: GPL-2.0
3 * Expose a PWM controlled by the ChromeOS EC to the host processor.
12 #include <linux/pwm.h>
16 * struct cros_ec_pwm_device - Driver data for EC PWM
20 * @chip: PWM controller chip
29 * struct cros_ec_pwm - per-PWM driver data
41 static int cros_ec_pwm_request(struct pwm_chip *chip, struct pwm_device *pwm) in cros_ec_pwm_request() argument
47 return -ENOMEM; in cros_ec_pwm_request()
49 pwm_set_chip_data(pwm, channel); in cros_ec_pwm_request()
54 static void cros_ec_pwm_free(struct pwm_chip *chip, struct pwm_device *pwm) in cros_ec_pwm_free() argument
[all …]
/kernel/linux/linux-5.10/include/linux/
Dpwm.h1 /* SPDX-License-Identifier: GPL-2.0 */
15 * enum pwm_polarity - polarity of a PWM signal
16 * @PWM_POLARITY_NORMAL: a high signal for the duration of the duty-
19 * @PWM_POLARITY_INVERSED: a low signal for the duration of the duty-
29 * struct pwm_args - board-dependent PWM arguments
33 * This structure describes board-dependent arguments attached to a PWM
34 * device. These arguments are usually retrieved from the PWM lookup table or
37 * Do not confuse this with the PWM state: PWM arguments represent the initial
38 * configuration that users want to use on this PWM device rather than the
39 * current PWM hardware state.
[all …]
/kernel/linux/linux-5.10/drivers/gpu/drm/amd/pm/powerplay/hwmgr/
Dpptable_v1_0.h45 …* To keep the number of these types low we should also use the same code for all ASICs (i.e. do no…
166 UCHAR ucNumEntries; /* Number of entries. */
181 UCHAR ucNumEntries; /* Number of entries. */
196 UCHAR ucNumEntries; /* Number of entries. */
212 UCHAR ucNumEntries; /* Number of entries. */
224 UCHAR ucNumEntries; /* Number of entries. */
237 UCHAR ucNumEntries; /* Number of entries. */
245 ULONG ulDClk; /* UVD D-clock */
246 ULONG ulVClk; /* UVD V-clock */
254 UCHAR ucNumEntries; /* Number of entries. */
[all …]
/kernel/linux/linux-5.10/include/linux/mfd/
Dlp8788.h1 /* SPDX-License-Identifier: GPL-2.0-only */
15 #include <linux/pwm.h>
18 #define LP8788_DEV_BUCK "lp8788-buck"
19 #define LP8788_DEV_DLDO "lp8788-dldo"
20 #define LP8788_DEV_ALDO "lp8788-aldo"
21 #define LP8788_DEV_CHARGER "lp8788-charger"
22 #define LP8788_DEV_RTC "lp8788-rtc"
23 #define LP8788_DEV_BACKLIGHT "lp8788-backlight"
24 #define LP8788_DEV_VIBRATOR "lp8788-vibrator"
25 #define LP8788_DEV_KEYLED "lp8788-keyled"
[all …]
/kernel/linux/linux-5.10/drivers/staging/greybus/
Dpwm.c1 // SPDX-License-Identifier: GPL-2.0
3 * PWM Greybus driver.
12 #include <linux/pwm.h>
19 u8 pwm_max; /* max pwm number */
22 struct pwm_chip *pwm; member
33 ret = gb_operation_sync(pwmc->connection, GB_PWM_TYPE_PWM_COUNT, in gb_pwm_count_operation()
37 pwmc->pwm_max = response.count; in gb_pwm_count_operation()
48 if (which > pwmc->pwm_max) in gb_pwm_activate_operation()
49 return -EINVAL; in gb_pwm_activate_operation()
53 gbphy_dev = to_gbphy_dev(pwmc->chip.dev); in gb_pwm_activate_operation()
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-mt7622.txt4 - compatible: Should be one of the following
5 "mediatek,mt7622-pinctrl" for MT7622 SoC
6 "mediatek,mt7629-pinctrl" for MT7629 SoC
7 - reg: offset and length of the pinctrl space
9 - gpio-controller: Marks the device node as a GPIO controller.
10 - #gpio-cells: Should be two. The first cell is the pin number and the
14 - interrupt-controller : Marks the device node as an interrupt controller
16 If the property interrupt-controller is defined, following property is required
17 - reg-names: A string describing the "reg" entries. Must contain "eint".
18 - interrupts : The interrupt output from the controller.
[all …]
/kernel/linux/linux-5.10/drivers/scsi/ufs/
Dufshcd-pltfrm.h1 /* SPDX-License-Identifier: GPL-2.0-only */
14 u32 pwm_rx_gear; /* pwm rx gear to work in */
15 u32 pwm_tx_gear; /* pwm tx gear to work in */
18 u32 rx_lanes; /* number of rx lanes */
19 u32 tx_lanes; /* number of tx lanes */
20 u32 rx_pwr_pwm; /* rx pwm working pwr */
21 u32 tx_pwr_pwm; /* tx pwm working pwr */
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/backlight/
Dpwm-backlight.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/leds/backlight/pwm-backlight.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: pwm-backlight bindings
10 - Lee Jones <lee.jones@linaro.org>
11 - Daniel Thompson <daniel.thompson@linaro.org>
12 - Jingoo Han <jingoohan1@gmail.com>
16 const: pwm-backlight
21 pwm-names: true
[all …]

123456789