Home
last modified time | relevance | path

Searched +full:gpio +full:- +full:controlled (Results 1 – 25 of 683) sorted by relevance

12345678910>>...28

/kernel/linux/linux-6.6/include/dt-bindings/sound/
Dcs35l45.h1 /* SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause */
3 * cs35l45.h -- CS35L45 ALSA SoC audio driver DT bindings header
12 * cirrus,asp-sdout-hiz-ctrl
14 * TX_HIZ_UNUSED: TX pin high-impedance during unused slots.
15 * TX_HIZ_DISABLED: TX pin high-impedance when all channels disabled.
21 * Optional GPIOX Sub-nodes:
22 * The cs35l45 node can have up to three "cirrus,gpio-ctrlX" ('X' = [1,2,3])
23 * sub-nodes for configuring the GPIO pins.
25 * - gpio-dir : GPIO pin direction. Valid only when 'gpio-ctrl'
30 * - gpio-lvl : GPIO level. Valid only when 'gpio-ctrl' is 1 and 'gpio-dir' is 0.
[all …]
/kernel/linux/linux-5.10/drivers/leds/trigger/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
15 This allows LEDs to be controlled by a programmable timer
18 For more details read Documentation/leds/leds-class.rst.
23 tristate "LED One-shot Trigger"
25 This allows LEDs to blink in one-shot pulses with parameters
26 controlled via sysfs. It's useful to notify the user on
39 This allows LEDs to be controlled by disk activity.
46 This allows LEDs to be controlled by MTD activity.
52 This allows LEDs to be controlled by a CPU load average.
53 The flash frequency is a hyperbolic function of the 1-minute
[all …]
/kernel/linux/linux-5.10/drivers/mux/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
22 be called mux-adg792a.
32 be called mux-adgs1408.
35 tristate "GPIO-controlled Multiplexer"
38 GPIO-controlled Multiplexer controller.
41 of gpio pins. For N pins, there will be 2^N possible multiplexer
42 states. The GPIO pins can be connected (by the hardware) to several
46 be called mux-gpio.
49 tristate "MMIO/Regmap register bitfield-controlled Multiplexer"
52 MMIO/Regmap register bitfield-controlled Multiplexer controller.
[all …]
/kernel/linux/linux-6.6/drivers/mux/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
22 be called mux-adg792a.
32 be called mux-adgs1408.
35 tristate "GPIO-controlled Multiplexer"
38 GPIO-controlled Multiplexer controller.
41 of gpio pins. For N pins, there will be 2^N possible multiplexer
42 states. The GPIO pins can be connected (by the hardware) to several
46 be called mux-gpio.
49 tristate "MMIO/Regmap register bitfield-controlled Multiplexer"
52 MMIO/Regmap register bitfield-controlled Multiplexer controller.
[all …]
/kernel/linux/linux-6.6/drivers/leds/trigger/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
15 This allows LEDs to be controlled by a programmable timer
18 For more details read Documentation/leds/leds-class.rst.
23 tristate "LED One-shot Trigger"
25 This allows LEDs to blink in one-shot pulses with parameters
26 controlled via sysfs. It's useful to notify the user on
39 This allows LEDs to be controlled by disk activity.
46 This allows LEDs to be controlled by MTD activity.
52 This allows LEDs to be controlled by a CPU load average.
53 The flash frequency is a hyperbolic function of the 1-minute
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/sound/
Dcirrus,cs35l45.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Ricardo Rivera-Matos <rriveram@opensource.cirrus.com>
11 - Richard Fitzgerald <rf@opensource.cirrus.com>
18 - $ref: dai-common.yaml#
23 - cirrus,cs35l45
28 '#sound-dai-cells':
31 reset-gpios:
34 vdd-a-supply:
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/
Dleds-bcm6328.txt6 controller), which can either be controlled by software (exporting the 74x164
7 as spi-gpio. See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or
9 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and
10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
11 controlled, so the only chance to keep them working is by using this driver.
14 should be controlled by a hardware signal instead of the MODE register value,
18 explained later in brcm,link-signal-sources). Even if a LED is hardware
19 controlled you are still able to make it blink or light it up if it isn't,
21 reason, hardware controlled LEDs aren't registered as LED class devices.
24 - compatible : should be "brcm,bcm6328-leds".
[all …]
/kernel/linux/linux-5.10/drivers/pinctrl/nomadik/
Dpinctrl-ab8500.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) ST-Ericsson SA 2012
5 * Author: Patrice Chotard <patrice.chotard@stericsson.com> for ST-Ericsson.
9 #include <linux/gpio/driver.h>
12 #include "pinctrl-abx500.h"
14 /* All the pins that can be used for GPIO and some other functions */
60 /* indicates the highest GPIO number */
64 * The names of the pins are denoted by GPIO number and ball name, even
65 * though they can be used for other things than GPIO, this is the first
115 * Maps local GPIO offsets to local pin numbers
[all …]
Dpinctrl-ab8505.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) ST-Ericsson SA 2012
5 * Author: Patrice Chotard <patrice.chotard@stericsson.com> for ST-Ericsson.
9 #include <linux/gpio/driver.h>
12 #include "pinctrl-abx500.h"
14 /* All the pins that can be used for GPIO and some other functions */
42 /* indicates the higher GPIO number */
46 * The names of the pins are denoted by GPIO number and ball name, even
47 * though they can be used for other things than GPIO, this is the first
79 * Maps local GPIO offsets to local pin numbers
[all …]
/kernel/linux/linux-6.6/drivers/pinctrl/nomadik/
Dpinctrl-ab8500.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) ST-Ericsson SA 2012
5 * Author: Patrice Chotard <patrice.chotard@stericsson.com> for ST-Ericsson.
13 #include "pinctrl-abx500.h"
15 /* All the pins that can be used for GPIO and some other functions */
61 /* indicates the highest GPIO number */
65 * The names of the pins are denoted by GPIO number and ball name, even
66 * though they can be used for other things than GPIO, this is the first
116 * Maps local GPIO offsets to local pin numbers
311 AB8500_FUNC_GROUPS(gpio, "gpio1_a_1", "gpio2_a_1", "gpio3_a_1", "gpio4_a_1",
[all …]
Dpinctrl-ab8505.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) ST-Ericsson SA 2012
5 * Author: Patrice Chotard <patrice.chotard@stericsson.com> for ST-Ericsson.
13 #include "pinctrl-abx500.h"
15 /* All the pins that can be used for GPIO and some other functions */
43 /* indicates the higher GPIO number */
47 * The names of the pins are denoted by GPIO number and ball name, even
48 * though they can be used for other things than GPIO, this is the first
80 * Maps local GPIO offsets to local pin numbers
197 AB8505_FUNC_GROUPS(gpio, "gpio1_a_1", "gpio2_a_1", "gpio3_a_1",
[all …]
/kernel/linux/linux-5.10/drivers/i2c/muxes/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
10 tristate "GPIO-based I2C arbitration"
17 a GPIO.
20 will be called i2c-arb-gpio-challenge.
23 tristate "GPIO-based I2C multiplexer"
27 GPIO based I2C multiplexer. This driver provides access to
28 I2C busses connected through a MUX, which is controlled
29 through GPIO pins.
32 will be called i2c-mux-gpio.
41 I2C busses connected through a MUX, which in turn is controlled
[all …]
/kernel/linux/linux-6.6/drivers/i2c/muxes/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
10 tristate "GPIO-based I2C arbitration"
17 a GPIO.
20 will be called i2c-arb-gpio-challenge.
23 tristate "GPIO-based I2C multiplexer"
27 GPIO based I2C multiplexer. This driver provides access to
28 I2C busses connected through a MUX, which is controlled
29 through GPIO pins.
32 will be called i2c-mux-gpio.
41 I2C busses connected through a MUX, which in turn is controlled
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/leds/
Dleds-bcm6328.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-bcm6328.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Álvaro Fernández Rojas <noltari@gmail.com>
16 controller), which can either be controlled by software (exporting the 74x164
17 as spi-gpio. See
18 Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml), or by hardware
20 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and
21 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
[all …]
/kernel/linux/linux-5.10/drivers/net/mdio/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
20 loadable module or built-in.
44 tristate "APM X-Gene SoC MDIO bus controller"
48 APM X-Gene SoC's.
57 third revision of the ASPEED MDIO register interface - the first two
94 tristate "GPIO lib-based bitbanged MDIO buses"
98 Supports GPIO lib-based MDIO busses.
101 will be called mdio-gpio.
160 IPQ40xx series Soc-s.
215 tristate "GPIO controlled MDIO bus multiplexers"
[all …]
/kernel/linux/linux-6.6/arch/arm/boot/dts/nxp/imx/
Dimx6qdl-dhcom-drc02.dtsi1 // SPDX-License-Identifier: GPL-2.0+
8 stdout-path = "serial0:115200n8";
25 * NOTE: On DRC02, the RS485_RX_En is controlled by a separate
26 * GPIO line, however the i.MX6 UART driver assumes RX happens
30 rs485-rx-en-hog {
31 gpio-hog;
32 gpios = <18 0>; /* GPIO Q */
33 line-name = "rs485-rx-en";
34 output-low;
39 gpio-line-names =
[all …]
/kernel/linux/linux-6.6/drivers/net/mdio/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
20 loadable module or built-in.
58 tristate "APM X-Gene SoC MDIO bus controller"
62 APM X-Gene SoC's.
72 third revision of the ASPEED MDIO register interface - the first two
109 tristate "GPIO lib-based bitbanged MDIO buses"
113 Supports GPIO lib-based MDIO busses.
116 will be called mdio-gpio.
177 IPQ40xx, IPQ60xx, IPQ807x and IPQ50xx series Soc-s.
193 layout. It's regmap-based so that it can be used on integrated,
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/regulator/
Dsamsung,s5m8767.txt4 This is a part of device tree bindings for S5M family multi-function devices.
5 More information can be found in bindings/mfd/sec-core.txt file.
10 a sub-node named "regulators" with more sub-nodes for each regulator using the
12 - Documentation/devicetree/bindings/regulator/regulator.txt
16 - s5m8767,pmic-buck-ds-gpios: GPIO specifiers for three host gpio's used
17 for selecting GPIO DVS lines. It is one-to-one mapped to dvs gpio lines.
19 [1] If either of the 's5m8767,pmic-buck[2/3/4]-uses-gpio-dvs' optional
21 's5m8767,pmic-buck[2/3/4]-dvs-voltage' should be specified.
24 - s5m8767,pmic-buck2-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
25 units for buck2 when changing voltage using gpio dvs. Refer to [1] below
[all …]
Dmax8997-regulator.txt3 The Maxim MAX8997 is a multi-function device which includes voltage and
4 current regulators, rtc, charger controller and other sub-blocks. It is
5 interfaced to the host controller using a i2c interface. Each sub-block is
7 describes the bindings for 'pmic' sub-block of max8997.
10 - compatible: Should be "maxim,max8997-pmic".
11 - reg: Specifies the i2c slave address of the pmic block. It should be 0x66.
13 - max8997,pmic-buck1-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
14 units for buck1 when changing voltage using gpio dvs. Refer to [1] below
17 - max8997,pmic-buck2-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
18 units for buck2 when changing voltage using gpio dvs. Refer to [1] below
[all …]
Dgpio-regulator.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/regulator/gpio-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: GPIO controlled regulators
10 - Liam Girdwood <lgirdwood@gmail.com>
11 - Mark Brown <broonie@kernel.org>
18 - $ref: "regulator.yaml#"
22 const: regulator-gpio
24 regulator-name: true
[all …]
Dtps65090.txt4 - compatible: "ti,tps65090"
5 - reg: I2C slave address
6 - interrupts: the interrupt outputs of the controller
7 - regulators: A node that houses a sub-node for each regulator within the
8 device. Each sub-node is identified using the node's name, with valid
9 values listed below. The content of each sub-node is defined by the
11 dcdc[1-3], fet[1-7] and ldo[1-2] respectively.
12 - vsys[1-3]-supply: The input supply for DCDC[1-3] respectively.
13 - infet[1-7]-supply: The input supply for FET[1-7] respectively.
14 - vsys-l[1-2]-supply: The input supply for LDO[1-2] respectively.
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/regulator/
Dgpio-regulator.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/regulator/gpio-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: GPIO controlled regulators
10 - Liam Girdwood <lgirdwood@gmail.com>
11 - Mark Brown <broonie@kernel.org>
18 - $ref: regulator.yaml#
22 const: regulator-gpio
24 regulator-name: true
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/media/i2c/
Dmaxim,max9286.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Jacopo Mondi <jacopo+renesas@jmondi.org>
12 - Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
13 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
14 - Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
18 Serial Links (GMSL) and outputs them on a CSI-2 D-PHY port using up to 4 data
28 '#address-cells':
31 '#size-cells':
[all …]
/kernel/linux/linux-6.6/include/linux/regulator/
Dmax8973-regulator.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * max8973-regulator.h -- MAXIM 8973 regulator
5 * Interface for regulator driver for MAXIM 8973 DC-DC step-down
38 * struct max8973_regulator_platform_data - max8973 regulator platform data.
51 * @enable_gpio: Enable GPIO. If EN pin is controlled through GPIO from host
52 * then GPIO number can be provided. If no GPIO controlled then
53 * it should be -1.
54 * @dvs_gpio: GPIO for dvs. It should be -1 if this is tied with fixed logic.
/kernel/linux/linux-5.10/include/linux/regulator/
Dmax8973-regulator.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * max8973-regulator.h -- MAXIM 8973 regulator
5 * Interface for regulator driver for MAXIM 8973 DC-DC step-down
38 * struct max8973_regulator_platform_data - max8973 regulator platform data.
51 * @enable_gpio: Enable GPIO. If EN pin is controlled through GPIO from host
52 * then GPIO number can be provided. If no GPIO controlled then
53 * it should be -1.
54 * @dvs_gpio: GPIO for dvs. It should be -1 if this is tied with fixed logic.

12345678910>>...28