| /kernel/linux/linux-6.6/Documentation/hwmon/ |
| D | tc654.rst | 13 - Chris Packham <chris.packham@alliedtelesis.co.nz>
14 - Masahiko Iwamoto <iwamoto@allied-telesis.co.jp>
17 -----------
20 The TC654 uses the 2-wire interface compatible with the SMBUS 2.0
22 one (1) PWM output which can be used for fan control.
25 -------------------
26 Ordinarily the pwm1_mode ABI is used for controlling the pwm output
27 mode. However, for this chip the output is always pwm, and the
28 pwm1_mode determines if the pwm output is controlled via the pwm1 value
32 Setting pwm1_mode to 1 will cause the pwm output to be driven based on
[all …]
|
| D | max31760.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later
19 -----------
21 The MAX31760 integrates temperature sensing along with precision PWM fan
23 temperature of a discrete diode-connected transistor, such as a 2N3906,
27 I2C-compatible interface. Fan speed is controlled based on the temperature
28 reading as an index to a 48-byte lookup table (LUT) containing
29 user-programmed PWM values. The flexible LUT-based architecture enables
35 remote high-temperature threshold has been exceeded.
37 Temperature measurement range: from -55°C to 125°C
41 Please refer how to instantiate this driver: Documentation/i2c/instantiating-devices.rst
[all …]
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | tc654.rst | 13 - Chris Packham <chris.packham@alliedtelesis.co.nz>
14 - Masahiko Iwamoto <iwamoto@allied-telesis.co.jp>
17 -----------
20 The TC654 uses the 2-wire interface compatible with the SMBUS 2.0
22 one (1) PWM output which can be used for fan control.
25 -------------------
26 Ordinarily the pwm1_mode ABI is used for controlling the pwm output
27 mode. However, for this chip the output is always pwm, and the
28 pwm1_mode determines if the pwm output is controlled via the pwm1 value
32 Setting pwm1_mode to 1 will cause the pwm output to be driven based on
[all …]
|
| /kernel/linux/linux-5.10/drivers/pwm/ |
| D | pwm-tegra.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * drivers/pwm/pwm-tegra.c
5 * Tegra pulse-width-modulation controller driver
7 * Copyright (c) 2010-2020, NVIDIA Corporation.
8 * Based on arch/arm/plat-mxc/pwm.c by Sascha Hauer <s.hauer@pengutronix.de>
11 * 1. 13-bit: Frequency division (SCALE)
12 * 2. 8-bit : Pulse division (DUTY)
13 * 3. 1-bit : Enable bit
15 * The PWM clock frequency is divided by 256 before subdividing it based
17 * frequency for PWM output. The maximum output frequency that can be
[all …]
|
| D | pwm-omap-dmtimer.c | 1 // SPDX-License-Identifier: GPL-2.0-only
6 * Heavily based on earlier code which is:
9 * Also based on pwm-samsung.c
13 * PWM driver / controller, using the OMAP's dual-mode timers
15 * reloaded with the load value and the pwm output goes up.
20 * - When PWM is stopped, timer counter gets stopped immediately. This
21 * doesn't allow the current PWM period to complete and stops abruptly.
22 * - When PWM is running and changing both duty cycle and period,
25 * is updated while the pwm pin is high, current pwm period/duty_cycle
26 * can get updated as below based on the current timer counter:
[all …]
|
| /kernel/linux/linux-6.6/drivers/pwm/ |
| D | pwm-omap-dmtimer.c | 1 // SPDX-License-Identifier: GPL-2.0-only
6 * Heavily based on earlier code which is:
9 * Also based on pwm-samsung.c
13 * PWM driver / controller, using the OMAP's dual-mode timers
15 * reloaded with the load value and the pwm output goes up.
20 * - When PWM is stopped, timer counter gets stopped immediately. This
21 * doesn't allow the current PWM period to complete and stops abruptly.
22 * - When PWM is running and changing both duty cycle and period,
25 * is updated while the pwm pin is high, current pwm period/duty_cycle
26 * can get updated as below based on the current timer counter:
[all …]
|
| D | pwm-clk.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * Clock based PWM controller
7 * This is an "adapter" driver that allows PWM consumers to use
8 * system clocks with duty cycle control as PWM outputs.
11 * - Due to the fact that exact behavior depends on the underlying
13 * - Underlying clock may not be able to give 0% or 100% duty cycle
15 * - When the PWM is disabled, the clock will be disabled as well,
17 * - The clk API doesn't expose the necessary calls to implement
28 #include <linux/pwm.h>
38 static int pwm_clk_apply(struct pwm_chip *chip, struct pwm_device *pwm, in pwm_clk_apply() argument
[all …]
|
| D | pwm-tegra.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * drivers/pwm/pwm-tegra.c
5 * Tegra pulse-width-modulation controller driver
7 * Copyright (c) 2010-2020, NVIDIA Corporation.
8 * Based on arch/arm/plat-mxc/pwm.c by Sascha Hauer <s.hauer@pengutronix.de>
11 * 1. 13-bit: Frequency division (SCALE)
12 * 2. 8-bit : Pulse division (DUTY)
13 * 3. 1-bit : Enable bit
15 * The PWM clock frequency is divided by 256 before subdividing it based
17 * frequency for PWM output. The maximum output frequency that can be
[all …]
|
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
2 menuconfig PWM config
3 bool "Pulse-Width Modulation (PWM) Support"
5 Generic Pulse-Width Modulation (PWM) support.
7 In Pulse-Width Modulation, a variation of the width of pulses
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
[all …]
|
| /kernel/linux/linux-5.10/drivers/video/backlight/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
14 This framework adds support for low-level control of LCD.
15 Some framebuffer devices connect to platform-specific LCD modules
16 in order to have a platform-specific way to control the flat panel
62 If you have a panel based on the ILI9221/9222 controller
69 If you have a panel based on the ILI9320 controller chip
84 If you have a VGG2432A4 panel based on the ILI9320 controller chip
90 This driver provides a platform-device registered LCD power
94 tristate "Sharp SL-6000 LCD Driver"
97 If you have an Sharp SL-6000 Zaurus say Y to enable a driver
[all …]
|
| /kernel/linux/linux-6.6/drivers/video/backlight/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
14 This framework adds support for low-level control of LCD.
15 Some framebuffer devices connect to platform-specific LCD modules
16 in order to have a platform-specific way to control the flat panel
62 If you have a panel based on the ILI9221/9222 controller
69 If you have a panel based on the ILI9320 controller chip
84 If you have a VGG2432A4 panel based on the ILI9320 controller chip
90 This driver provides a platform-device registered LCD power
118 tristate "Himax HX-8357 LCD Driver"
121 If you have a HX-8357 LCD panel, say Y to enable its LCD control
[all …]
|
| /kernel/linux/linux-5.10/drivers/leds/ |
| D | leds-pwm.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * linux/drivers/leds-pwm.c
5 * simple PWM based LED control
9 * based on leds-gpio.c by Raphael Assenat <raph@8d.com>
18 #include <linux/pwm.h>
29 struct pwm_device *pwm; member
44 unsigned int max = led_dat->cdev.max_brightness; in led_pwm_set()
45 unsigned long long duty = led_dat->pwmstate.period; in led_pwm_set()
50 if (led_dat->active_low) in led_pwm_set()
51 duty = led_dat->pwmstate.period - duty; in led_pwm_set()
[all …]
|
| /kernel/linux/linux-6.6/drivers/leds/ |
| D | leds-pwm.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * linux/drivers/leds-pwm.c
5 * simple PWM based LED control
9 * based on leds-gpio.c by Raphael Assenat <raph@8d.com>
18 #include <linux/pwm.h>
31 struct pwm_device *pwm; member
46 unsigned int max = led_dat->cdev.max_brightness; in led_pwm_set()
47 unsigned long long duty = led_dat->pwmstate.period; in led_pwm_set()
52 if (led_dat->active_low) in led_pwm_set()
53 duty = led_dat->pwmstate.period - duty; in led_pwm_set()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pwm/ |
| D | pwm.txt | 1 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 …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pwm/ |
| D | pwm.txt | 1 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 …]
|
| D | clk-pwm.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/pwm/clk-pwm.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Clock based PWM controller
10 - Nikita Travkin <nikita@trvn.ru>
15 It's often possible to control duty-cycle of such clocks which makes them
16 suitable for generating PWM signal.
19 - $ref: pwm.yaml#
23 const: clk-pwm
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | exynos4412-odroidu3.dts | 1 // SPDX-License-Identifier: GPL-2.0
3 * Hardkernel's Exynos4412 based ODROID-U3 board device tree source
7 * Device tree source file for Hardkernel's ODROID-U3 board which is based
11 /dts-v1/;
12 #include "exynos4412-odroid-common.dtsi"
13 #include "exynos4412-prime.dtsi"
16 model = "Hardkernel ODROID-U3 board based on Exynos4412";
17 compatible = "hardkernel,odroid-u3", "samsung,exynos4412", "samsung,exynos4";
25 compatible = "gpio-leds";
29 default-state = "on";
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/backlight/ |
| D | lp855x-driver.rst | 15 -----------
19 Brightness can be controlled by the pwm input or the i2c command.
28 Value: pwm based or register based
37 ------------------------
48 Platform specific PWM period value. unit is nano.
49 Only valid when brightness is pwm input mode.
68 .name = "lcd-bl",
75 2) lp8556 platform data: pwm input mode with default rom data::
|
| /kernel/linux/linux-5.10/Documentation/driver-api/backlight/ |
| D | lp855x-driver.rst | 15 -----------
19 Brightness can be controlled by the pwm input or the i2c command.
28 Value: pwm based or register based
37 ------------------------
48 Platform specific PWM period value. unit is nano.
49 Only valid when brightness is pwm input mode.
68 .name = "lcd-bl",
75 2) lp8556 platform data: pwm input mode with default rom data::
|
| /kernel/linux/linux-5.10/drivers/input/misc/ |
| D | pwm-vibra.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * PWM vibrator driver
7 * Based on previous work from:
10 * Based on PWM beeper driver:
11 * Copyright (C) 2010, Lars-Peter Clausen <lars@metafoo.de>
20 #include <linux/pwm.h>
26 struct pwm_device *pwm; member
38 struct device *pdev = vibrator->input->dev.parent; in pwm_vibrator_start()
42 if (!vibrator->vcc_on) { in pwm_vibrator_start()
43 err = regulator_enable(vibrator->vcc); in pwm_vibrator_start()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/input/ |
| D | pwm-vibrator.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/pwm-vibrator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: PWM vibrator
10 - Sebastian Reichel <sre@kernel.org>
13 Registers a PWM device as vibrator. It is expected, that the vibrator's
14 strength increases based on the duty cycle of the enable PWM channel
17 The binding supports an optional direction PWM channel, that can be
23 const: pwm-vibrator
[all …]
|
| /kernel/linux/linux-6.6/drivers/input/misc/ |
| D | pwm-vibra.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * PWM vibrator driver
7 * Based on previous work from:
10 * Based on PWM beeper driver:
11 * Copyright (C) 2010, Lars-Peter Clausen <lars@metafoo.de>
21 #include <linux/pwm.h>
28 struct pwm_device *pwm; member
40 struct device *pdev = vibrator->input->dev.parent; in pwm_vibrator_start()
44 if (!vibrator->vcc_on) { in pwm_vibrator_start()
45 err = regulator_enable(vibrator->vcc); in pwm_vibrator_start()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/ |
| D | pwm-vibrator.txt | 1 * PWM vibrator device tree bindings
3 Registers a PWM device as vibrator. It is expected, that the vibrator's
4 strength increases based on the duty cycle of the enable PWM channel
7 The binding supports an optional direction PWM channel, that can be
12 - compatible: should contain "pwm-vibrator"
13 - pwm-names: Should contain "enable" and optionally "direction"
14 - pwms: Should contain a PWM handle for each entry in pwm-names
17 - vcc-supply: Phandle for the regulator supplying power
18 - direction-duty-cycle-ns: Duty cycle of the direction PWM channel in
26 pinctrl-single,pins = <
[all …]
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/samsung/ |
| D | exynos4412-odroidu3.dts | 1 // SPDX-License-Identifier: GPL-2.0
3 * Hardkernel's Exynos4412 based ODROID-U3 board device tree source
7 * Device tree source file for Hardkernel's ODROID-U3 board which is based
11 /dts-v1/;
12 #include <dt-bindings/leds/common.h>
13 #include "exynos4412-odroid-common.dtsi"
14 #include "exynos4412-prime.dtsi"
17 model = "Hardkernel ODROID-U3 board based on Exynos4412";
18 compatible = "hardkernel,odroid-u3", "samsung,exynos4412", "samsung,exynos4";
29 vbus_otg_reg: regulator-1 {
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/mach-s3c/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
5 source "arch/arm/mach-s3c/Kconfig.s3c24xx"
6 source "arch/arm/mach-s3c/Kconfig.s3c64xx"
16 Base platform code for all Samsung SoC based systems
33 int "S3C UART to use for low-level messages"
37 Choice of which UART port to use for the low-level messages,
40 must have been initialised by the boot-loader before use.
46 This option enables ATAGS based boot support code for
50 Platforms that support only DT based boot need not to select
155 Compile in platform device definition for USB high-speed OtG
[all …]
|