| /Zephyr-latest/samples/subsys/modbus/rtu_server/ |
| D | sample.yaml | 7 - nrf52840dk/nrf52840
8 - frdm_k64f
10 - nrf52840dk/nrf52840
12 - uart
13 - modbus
14 filter: dt_enabled_alias_with_parent_compat("led0", "gpio-leds") and
15 dt_enabled_alias_with_parent_compat("led1", "gpio-leds") and
16 dt_enabled_alias_with_parent_compat("led2", "gpio-leds")
18 - gpio
19 - arduino_serial
[all …]
|
| /Zephyr-latest/dts/bindings/led/ |
| D | gpio-leds.yaml | 2 # SPDX-License-Identifier: Apache-2.0
5 This allows you to define a group of LEDs. Each LED in the group is
6 controlled by a GPIO. Each LED is defined in a child node of the
7 gpio-leds node.
9 Here is an example which defines three LEDs in the node /leds:
12 leds {
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,
[all …]
|
| /Zephyr-latest/samples/subsys/modbus/tcp_server/ |
| D | sample.yaml | 8 - frdm_k64f
10 filter: dt_enabled_alias_with_parent_compat("led0", "gpio-leds") and
11 dt_enabled_alias_with_parent_compat("led1", "gpio-leds") and
12 dt_enabled_alias_with_parent_compat("led2", "gpio-leds")
14 - gpio
15 - netif
|
| /Zephyr-latest/samples/basic/blinky/ |
| D | README.rst | 1 .. zephyr:code-sample:: blinky
3 :relevant-api: gpio_interface
5 Blink an LED forever using the GPIO API.
10 The Blinky sample blinks an LED forever using the :ref:`GPIO API <gpio_api>`.
14 #. Get a pin specification from the :ref:`devicetree <dt-guide>` as a
16 #. Configure the GPIO pin as an output
19 See :zephyr:code-sample:`pwm-blinky` for a similar sample that uses the PWM API instead.
21 .. _blinky-sample-requirements:
28 #. Have an LED connected via a GPIO pin (these are called "User LEDs" on many of
37 .. zephyr-app-commands::
[all …]
|
| /Zephyr-latest/tests/drivers/gpio/gpio_api_1pin/ |
| D | testcase.yaml | 3 - drivers
4 - gpio
5 depends_on: gpio
8 drivers.gpio.1pin:
10 dt_enabled_alias_with_parent_compat("led0", "gpio-leds")
11 and not dt_compat_enabled("test-gpio-external-pulldown")
14 - mps2/an385
15 - mps2/an521/cpu0
16 - neorv32
17 drivers.gpio.1pin.aw9523b:
[all …]
|
| /Zephyr-latest/samples/basic/threads/ |
| D | sample.yaml | 2 description: A basic demo to showcase multi-threading using K_THREAD_DEFINE
7 - kernel
8 - threads
9 - gpio
10 filter: dt_enabled_alias_with_parent_compat("led0", "gpio-leds") and
11 dt_enabled_alias_with_parent_compat("led1", "gpio-leds")
13 - nrf52833dk/nrf52820
14 depends_on: gpio
20 - "Toggled led0; counter=(.*)"
21 - "Toggled led1; counter=(.*)"
|
| /Zephyr-latest/samples/drivers/led/apa102c_bitbang/src/ |
| D | main.c | 4 * SPDX-License-Identifier: Apache-2.0
11 * level shifter (preferred) or pull-up resistors are needed.
12 * Make sure the pins are 5V tolerant if using pull-up
16 * Protect your eyes and do not look directly into those LEDs.
24 #include <zephyr/drivers/gpio.h>
47 /* Number of LEDS linked together */
71 int leds = 0; in main() local
75 printk("GPIO device %s is not ready!\n", gpio_dev->name); in main()
79 /* Setup GPIO output */ in main()
93 for (leds = 0; leds < NUM_LEDS; leds++) { in main()
[all …]
|
| /Zephyr-latest/samples/drivers/led/pwm/boards/ |
| D | mr_canhubk3.conf | 2 # SPDX-License-Identifier: Apache-2.0
4 # Due to gpio-leds and pwm-leds are the same RGB LEDs so should not be used
5 # at the same time, need to disable this config when using pwm-leds.
|
| /Zephyr-latest/boards/nordic/nrf54l15dk/ |
| D | nrf54l15dk_common.dtsi | 4 * SPDX-License-Identifier: Apache-2.0
7 #include "nrf54l15dk_nrf54l_05_10_15-pinctrl.dtsi"
10 leds {
11 compatible = "gpio-leds";
31 compatible = "pwm-leds";
33 * PWM signal can be exposed on GPIO pin only within same domain.
34 * There is only one domain which contains both PWM and GPIO:
35 * PWM20/21/22 and GPIO Port P1.
36 * Only LEDs connected to P1 can work with PWM, for example LED1.
44 compatible = "gpio-keys";
[all …]
|
| /Zephyr-latest/boards/st/nucleo_h745zi_q/ |
| D | nucleo_h745zi_q.dtsi | 4 * SPDX-License-Identifier: Apache-2.0
7 #include <st/h7/stm32h745zitx-pinctrl.dtsi>
9 #include <zephyr/dt-bindings/input/input-event-codes.h>
12 leds: leds { label
13 compatible = "gpio-leds";
25 compatible = "gpio-keys";
|
| /Zephyr-latest/boards/raspberrypi/rpi_4b/ |
| D | rpi_4b.dts | 4 * SPDX-License-Identifier: Apache-2.0
7 /dts-v1/;
10 #include <zephyr/dt-bindings/gpio/gpio.h>
14 compatible = "raspberrypi,4-model-b", "brcm,bcm2838";
15 #address-cells = <1>;
16 #size-cells = <1>;
24 zephyr,shell-uart = &uart1;
28 leds {
29 compatible = "gpio-leds";
31 led_act: led-act {
[all …]
|
| /Zephyr-latest/tests/drivers/gpio/gpio_api_1pin/boards/ |
| D | up_squared.overlay | 4 * SPDX-License-Identifier: Apache-2.0
12 * () Advanced -> HAT Configurations:
13 * - HD-Audio / I2S6 Selec -> Disabled
15 * - GPIO 28 (Pin40) Confi -> Output
23 leds {
24 compatible = "gpio-leds";
|
| /Zephyr-latest/samples/drivers/led/xec/ |
| D | README.rst | 1 .. zephyr:code-sample:: led-xec
2 :name: Breathing-blinking LED (BBLED)
3 :relevant-api: led_interface
5 Control a BBLED (Breathing-Blinking LED) using Microchip XEC driver.
10 This sample allows to test the Microchip led-xec driver which uses the
11 breathing-blinking LED (BBLED) controllers. The SoC design is fixed
12 allowing each BBLED control over one specific GPIO.
16 - BBLED controller 0 uses GPIO 0156.
17 - BBLED controller 1 uses GPIO 0157.
18 - BBLED controller 2 uses GPIO 0153.
[all …]
|
| /Zephyr-latest/boards/st/nucleo_h755zi_q/ |
| D | nucleo_h755zi_q.dtsi | 4 * SPDX-License-Identifier: Apache-2.0
7 #include <st/h7/stm32h755zitx-pinctrl.dtsi>
9 #include <zephyr/dt-bindings/input/input-event-codes.h>
12 leds: leds { label
13 compatible = "gpio-leds";
29 compatible = "gpio-keys";
|
| /Zephyr-latest/boards/intel/socfpga_std/cyclonev_socdk/ |
| D | cyclonev_socdk.dts | 2 * SPDX-License-Identifier: Apache-2.0
10 #include <zephyr/dt-bindings/gpio/gpio.h>
14 compatible = "altr,socfpga-cyclonev-socdk", "altr,socfpga-cyclonev", "altr,socfpga";
23 /* Giving different names to the LEDs connected to the HPS side of the chip */
28 eeprom-0 = &eeprom;
31 leds {
32 compatible = "gpio-leds";
50 local-mac-address = [e6 88 2d 82 1f d4];
52 gpio0: gpio@ff708000 {
55 gpio1: gpio@ff709000 {
[all …]
|
| /Zephyr-latest/boards/st/stm32h745i_disco/ |
| D | stm32h745i_disco.dtsi | 5 * SPDX-License-Identifier: Apache-2.0
8 #include <st/h7/stm32h745xihx-pinctrl.dtsi>
10 #include <zephyr/dt-bindings/input/input-event-codes.h>
13 leds: leds { label
14 compatible = "gpio-leds";
30 compatible = "gpio-keys";
|
| /Zephyr-latest/boards/raspberrypi/rpi_5/ |
| D | rpi_5.dts | 4 * SPDX-License-Identifier: Apache-2.0
7 /dts-v1/;
10 #include <zephyr/dt-bindings/gpio/gpio.h>
13 compatible = "raspberrypi,5-model-b", "brcm,bcm2712";
15 #address-cells = <2>;
16 #size-cells = <1>;
25 zephyr,shell-uart = &uart10;
28 leds {
29 compatible = "gpio-leds";
31 led_act: led-act {
[all …]
|
| /Zephyr-latest/boards/st/nucleo_l452re/ |
| D | nucleo_l452re_stm32l452xx_p.dts | 5 * SPDX-License-Identifier: Apache-2.0
8 /dts-v1/;
10 #include <st/l4/stm32l452retxp-pinctrl.dtsi>
14 model = "STMicroelectronics STM32L452RE-P-NUCLEO board";
15 compatible = "st,stm32l452re-nucleo";
17 leds: leds { label
18 compatible = "gpio-leds";
|
| D | nucleo_l452re.dts | 5 * SPDX-License-Identifier: Apache-2.0
8 /dts-v1/;
10 #include <st/l4/stm32l452r(c-e)tx-pinctrl.dtsi>
15 model = "STMicroelectronics STM32L452RE-NUCLEO board";
16 compatible = "st,stm32l452re-nucleo";
18 leds: leds { label
19 compatible = "gpio-leds";
|
| /Zephyr-latest/boards/raspberrypi/common/ |
| D | rpi_pico-led.dtsi | 4 * SPDX-License-Identifier: Apache-2.0
9 leds {
10 compatible = "gpio-leds";
18 compatible = "pwm-leds";
28 pwm-led0 = &pwm_led0;
|
| /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/tests/drivers/gpio/gpio_get_direction/boards/ |
| D | nrf52_bsim.overlay | 4 * SPDX-License-Identifier: Apache-2.0
13 leds {
14 compatible = "gpio-leds";
|
| /Zephyr-latest/tests/drivers/gpio/gpio_get_direction/ |
| D | testcase.yaml | 2 drivers.gpio.get_direction:
4 - drivers
5 - gpio
6 depends_on: gpio
10 - mps2/an385
11 - mps2/an521/cpu0
12 - neorv32
13 filter: dt_enabled_alias_with_parent_compat("led0", "gpio-leds")
|
| /Zephyr-latest/boards/quicklogic/quick_feather/ |
| D | quick_feather.dts | 4 * SPDX-License-Identifier: Apache-2.0
7 /dts-v1/;
9 #include <zephyr/dt-bindings/pinctrl/quicklogic-eos-s3-pinctrl.h>
10 #include <zephyr/dt-bindings/input/input-event-codes.h>
19 zephyr,shell-uart = &uart0;
20 zephyr,uart-pipe = &uart0;
30 leds {
31 compatible = "gpio-leds";
33 gpios = <&gpio 4 GPIO_ACTIVE_HIGH>;
38 gpios = <&gpio 5 GPIO_ACTIVE_HIGH>;
[all …]
|
| /Zephyr-latest/boards/gd/gd32f407v_start/ |
| D | gd32f407v_start.dts | 3 * SPDX-License-Identifier: Apache-2.0
6 /dts-v1/;
9 #include "gd32f407v_start-pinctrl.dtsi"
10 #include <zephyr/dt-bindings/input/input-event-codes.h>
13 model = "GigaDevice GD32F407V-START";
14 compatible = "gd,gd32f407v-start";
20 zephyr,shell-uart = &usart0;
23 leds {
24 compatible = "gpio-leds";
31 compatible = "gpio-keys";
[all …]
|
