Searched +full:gpio +full:- +full:controlled (Results 1 – 25 of 92) sorted by relevance
1234
| /Zephyr-latest/drivers/regulator/ |
| D | Kconfig.gpio | 2 # SPDX-License-Identifier: Apache-2.0
5 bool "GPIO-controlled regulators"
8 select GPIO
10 Enable the driver for GPIO-controlled regulators
|
| D | Kconfig.fixed | 2 # SPDX-License-Identifier: Apache-2.0
5 bool "GPIO-controlled regulators"
8 depends on GPIO
10 Enable the driver for GPIO-controlled regulators
|
| /Zephyr-latest/drivers/can/transceiver/ |
| D | Kconfig | 4 # SPDX-License-Identifier: Apache-2.0
15 bool "GPIO controlled CAN transceiver"
18 select GPIO
20 Enable support for GPIO controlled CAN transceivers.
|
| /Zephyr-latest/dts/bindings/spi/ |
| D | nxp,s32-spi.yaml | 1 # Copyright 2022-2023 NXP
2 # SPDX-License-Identifier: Apache-2.0
6 compatible: "nxp,s32-spi"
8 include: [spi-controller.yaml, pinctrl-device.yaml]
17 num-cs:
26 pinctrl-0:
29 pinctrl-names:
37 spi-sck-cs-delay:
45 This value will not be applied for CS lines controlled by GPIO.
47 spi-cs-sck-delay:
[all …]
|
| /Zephyr-latest/dts/bindings/regulator/ |
| D | nordic,npm1300-regulator.yaml | 2 # SPDX-License-Identifier: Apache-2.0
16 compatible = "nordic,npm1300-regulator";
33 compatible: "nordic,npm1300-regulator"
38 dvs-gpios:
39 type: phandle-array
47 The effect of the mode change is defined by the enable-gpios
50 child-binding:
52 - name: regulator.yaml
53 property-allowlist:
54 - regulator-always-on
[all …]
|
| D | regulator-gpio.yaml | 2 # SPDX-License-Identifier: Apache-2.0
5 GPIO-controlled voltage of regulators
8 vccq_sd0: regulator-vccq-sd0 {
9 compatible = "regulator-gpio";
11 regulator-name = "SD0 VccQ";
12 regulator-min-microvolt = <1800000>;
13 regulator-max-microvolt = <3300000>;
15 enable-gpios = <&gpio5 3 GPIO_ACTIVE_HIGH>;
20 regulator-boot-on;
23 In the above example, three GPIO pins are used for controlling the regulator:
[all …]
|
| D | nordic,npm1100.yaml | 2 # SPDX-License-Identifier: Apache-2.0
18 Note that only mode can be controlled (via GPIO pin MODE).
25 nordic,iset-gpios:
26 type: phandle-array
30 child-binding:
32 nordic,mode-gpios:
33 type: phandle-array
38 - name: regulator.yaml
39 property-allowlist:
40 - regulator-allowed-modes
[all …]
|
| /Zephyr-latest/boards/arduino/opta/dts/bindings/ |
| D | gpio-power-switches.yaml | 2 # SPDX-License-Identifier: Apache-2.0
6 or other kinds of power switches controlled by a GPIO. Each power
7 switch is defined in a child node of the gpio-power-switches node.
9 compatible: "gpio-power-switches"
11 child-binding:
12 description: GPIO power switch child node
15 type: phandle-array
|
| /Zephyr-latest/dts/bindings/dac/ |
| D | espressif,esp32-dac.yaml | 2 # SPDX-License-Identifier: Apache-2.0
6 is part of the RTC low-power domain and belongs to the SENSE
7 peripherals set. RTC peripherals has GPIOs controlled by the
10 Two GPIO pads can only be connected to the DAC peripheral.
13 - GPIO25 as DAC channel 1
14 - GPIO26 as DAC channel 2
16 ESP32-S2 pads
17 - GPIO17 as DAC channel 1
18 - GPIO18 as DAC channel 2
28 properties 'dac-channel-id', which uses zero based channel index.
[all …]
|
| /Zephyr-latest/dts/bindings/phy/ |
| D | can-transceiver-gpio.yaml | 2 # SPDX-License-Identifier: Apache-2.0
4 description: Simple GPIO controlled CAN transceiver
6 compatible: "can-transceiver-gpio"
8 include: can-transceiver.yaml
11 enable-gpios:
12 type: phandle-array
14 GPIO to use to enable/disable the CAN transceiver. This GPIO is driven
18 standby-gpios:
19 type: phandle-array
21 GPIO to use to put the CAN transceiver into standby. This GPIO is driven
|
| /Zephyr-latest/dts/bindings/power-domain/ |
| D | power-domain-gpio.yaml | 2 # SPDX-License-Identifier: Apache-2.0
4 description: Simple GPIO controlled power domain
6 compatible: "power-domain-gpio"
8 include: power-domain.yaml
11 enable-gpios:
12 type: phandle-array
15 GPIO to use to enable/disable the regulator.
17 Unlike the gpio property in the Linux bindings this array must
18 provide the GPIO polarity and open-drain status in the phandle
19 selector. The Linux enable-active-high and gpio-open-drain
[all …]
|
| /Zephyr-latest/drivers/power_domain/ |
| D | Kconfig | 2 # SPDX-License-Identifier: Apache-2.0
12 module-str = power_domain
22 bool "GPIO controlled power domain"
25 depends on GPIO
33 int "GPIO power domain init priority"
36 GPIO power domain initialization priority.
59 bool "GPIO monitor for sensing power on rail"
62 depends on GPIO
69 int "GPIO monitor power domain init priority"
72 GPIO monitor power domain initialization priority.
[all …]
|
| /Zephyr-latest/boards/nxp/imx93_evk/dts/bindings/ |
| D | imx93evk-exp-sel.yaml | 2 # SPDX-License-Identifier: Apache-2.0
6 functions. They are controlled by EXP_SEL signal from gpio_exp0, an
7 ADP5585 GPIO expander.
9 compatible: "imx93evk-exp-sel"
14 mux-gpios:
15 type: phandle-array
23 - "A"
24 - "B"
|
| /Zephyr-latest/dts/bindings/led/ |
| D | gpio-leds.yaml | 2 # SPDX-License-Identifier: Apache-2.0
6 controlled by a GPIO. Each LED is defined in a child node of the
7 gpio-leds node.
13 compatible = "gpio-leds";
28 - led_0 is pin 1 on gpio0. The LED is on when the pin is low,
30 - led_1 is pin 2 on gpio0. The LED is on when the pin is high,
32 - led_2 is pin 15 on gpio1. The LED is on when the pin is low,
33 and the pin's internal pull-up resistor should be enabled.
35 compatible: "gpio-leds"
37 child-binding:
[all …]
|
| /Zephyr-latest/boards/shields/nrf7002ek/boards/ |
| D | nrf5340dk_nrf5340_cpuapp.overlay | 3 * SPDX-License-Identifier: Apache-2.0
7 * same pins as bucken and iovdd-ctrl, we need these pins to be controlled by
10 * to the CPUNET, it should create a separate instance of nrf-gpio-forwarder
|
| /Zephyr-latest/dts/bindings/lora/ |
| D | semtech,sx126x-base.yaml | 3 # SPDX-License-Identifier: Apache-2.0
5 include: spi-device.yaml
8 reset-gpios:
9 type: phandle-array
11 GPIO connected to the modem's NRESET signal.
13 This signal is open-drain, active-low as interpreted by the
16 busy-gpios:
17 type: phandle-array
19 GPIO connected to the modem's BUSY signal.
21 antenna-enable-gpios:
[all …]
|
| /Zephyr-latest/include/zephyr/drivers/gpio/ |
| D | gpio_sx1509b.h | 4 * SPDX-License-Identifier: Apache-2.0
11 #include <zephyr/drivers/gpio.h>
20 * Configure a pin to be controlled by SX1509B LED driver using
22 * To get back normal GPIO functionality, configure the pin using
23 * the standard GPIO API.
29 * @retval -EWOULDBLOCK if function is called from an ISR.
30 * @retval -ERANGE if pin number is out of range.
31 * @retval -EIO if I2C fails.
44 * @retval -EIO if I2C fails.
|
| /Zephyr-latest/include/zephyr/drivers/misc/ |
| D | README | 4 Zephyr Device Drivers API. Such drivers have only device-specific API providing
16 rendering. These operations are controlled by a vendor-specific API designed
19 * STM32 Wake-up Pins
20 STM32 wake-up pins are part of the Power Control (PWR) peripheral.
21 They can be used to wake-up the system from Poweroff through GPIO pins.
|
| /Zephyr-latest/samples/basic/custom_dts_binding/ |
| D | README.rst | 1 .. zephyr:code-sample:: gpio-custom-dts-binding
2 :name: GPIO with custom Devicetree binding
3 :relevant-api: gpio_interface devicetree-generic-id devicetree-generic-exist
5 Use custom Devicetree binding to control a GPIO.
10 In Zephyr, all hardware-specific configuration is described in the devicetree.
12 Consequently, also GPIO pins are configured in the devicetree and assigned to a specific purpose
16 output) of a GPIO pin is configured in the application firmware.
18 For typical use cases like LEDs or buttons, the existing :dtcompatible:`gpio-leds` or
19 :dtcompatible:`gpio-keys` compatibles can be used.
21 This sample demonstrates how to use a GPIO pin for other purposes with a custom devicetree binding.
[all …]
|
| /Zephyr-latest/dts/bindings/mmc/ |
| D | renesas,rcar-emmc.yaml | 1 description: Renesas R-Car eMMC
3 compatible: "renesas,rcar-mmc"
5 include: [sdhc.yaml, mmc.yaml, pinctrl-device.yaml, reset-device.yaml]
14 pinctrl-0:
17 pinctrl-names:
20 max-bus-freq:
23 non-removable:
26 Non-removable slots (like eMMC), which are assumed to always be present,
30 mmc-sdr104-support:
33 cd-gpios:
[all …]
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | regulators.rst | 7 example is a GPIO that controls a transistor that supplies current to a device
11 The ``*-supply`` devicetree properties are used to identify the regulator(s)
18 infrastructure is not justified, and ``*-gpios`` devicetree properties should be
20 controlled within the driver for the corresponding node, e.g. a sensor.
|
| /Zephyr-latest/dts/bindings/gpio/ |
| D | nordic,nrf-gpio-forwarder.yaml | 2 # SPDX-License-Identifier: Apache-2.0
7 In nRF53 family of SoCs, GPIO pins must be explicitly forwarded by
9 The purpose of this abstract device is to represent all GPIO pins that the
12 Once the control over selected GPIO pins is forwarded to it, the network
15 Here is an example of how a nrf-gpio-forwarder can be used with a nRF5340
16 combined with a nRF21540 Front-End module. Consider the following node
18 the details of the nRF21540 Front-End module's interface:
21 compatible = "nordic,nrf21540-fem";
22 tx-en-gpios = <&gpio0 30 GPIO_ACTIVE_HIGH>;
23 rx-en-gpios = <&gpio1 11 GPIO_ACTIVE_HIGH>;
[all …]
|
| /Zephyr-latest/soc/microchip/mec/mec15xx/ |
| D | Kconfig | 4 # SPDX-License-Identifier: Apache-2.0
41 By default these pins are not GPIOs, but HW controlled.
57 or other non-JTAG alternate functions.
62 JTAG port in SWD mode. UART2 and ADC00-03 can be used.
68 to see if ADC00-03 can be used or not.
83 UART2 can be used, but ADC00-03 cannot.
89 UART2 cannot be used. ADC00-03 can be used.
92 # GPIO initialization depends on SOC initialization, which happen at
95 if GPIO
100 endif # GPIO
|
| /Zephyr-latest/boards/gd/gd32vf103c_starter/ |
| D | gd32vf103c_starter.dts | 3 * SPDX-License-Identifier: Apache-2.0
6 /dts-v1/;
9 #include "gd32vf103c_starter-pinctrl.dtsi"
10 #include <zephyr/dt-bindings/input/input-event-codes.h>
13 model = "GigaDevice GD32VF103C-STARTER";
14 compatible = "gd,gd32vf103c-starter";
20 zephyr,shell-uart = &usart0;
21 zephyr,flash-controller = &fmc;
25 compatible = "gpio-leds";
33 compatible = "gpio-keys";
[all …]
|
| /Zephyr-latest/dts/bindings/can/ |
| D | can-controller.yaml | 6 bus-speed:
19 sample-point:
30 Actively controlled CAN transceiver.
33 transceiver0: can-phy0 {
34 compatible = "nxp,tja1040", "can-transceiver-gpio";
35 standby-gpios = <gpioa 0 GPIO_ACTIVE_HIGH>;
36 max-bitrate = <1000000>;
37 #phy-cells = <0>;
46 child-binding:
48 Passive CAN transceiver. The child node must be named "can-transceiver".
[all …]
|
1234
