/Zephyr-Core-3.5.0/samples/drivers/led_lp5562/ |
D | README.rst | 5 Control 4 RGB LEDs connected to an LP5562 driver chip. 10 This sample controls 4 LEDs connected to a TI LP5562 driver, using the 13 1. turn on LEDs to be red 14 2. turn on LEDs to be green 15 3. turn on LEDs to be blue 16 4. turn on LEDs to be white 17 5. turn on LEDs to be yellow 18 6. turn on LEDs to be purple 19 7. turn on LEDs to be cyan 20 8. turn on LEDs to be orange [all …]
|
/Zephyr-Core-3.5.0/samples/drivers/led_pwm/ |
D | README.rst | 5 Control PWM LEDs using the LED API. 10 This sample allows to test the led-pwm driver. The first "pwm-leds" compatible 11 device instance found in DT is used. For each LEDs attached to this device 13 functions are used to control the LEDs. 18 For each PWM LEDs (one after the other): 30 This sample can be built and executed on all the boards with PWM LEDs connected. 31 The LEDs must be correctly described in the DTS: the compatible property of the 32 device node must match "pwm-leds". And for each LED, a child node must be
|
/Zephyr-Core-3.5.0/samples/drivers/led_pca9633/ |
D | README.rst | 5 Control 4 LEDs connected to a PCA9633 driver chip. 10 This sample controls 4 LEDs connected to a PCA9633 driver, using the 13 1. turn on LEDs 14 2. turn off LEDs 16 4. turn off LEDs 17 5. blink the LEDs 18 6. turn off LEDs
|
/Zephyr-Core-3.5.0/samples/subsys/modbus/rtu_server/ |
D | sample.yaml | 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") 30 filter: dt_enabled_alias_with_parent_compat("led0", "gpio-leds") and 31 dt_enabled_alias_with_parent_compat("led1", "gpio-leds") and 32 dt_enabled_alias_with_parent_compat("led2", "gpio-leds")
|
/Zephyr-Core-3.5.0/samples/drivers/ht16k33/ |
D | README.rst | 5 Control up to 128 LEDs connected to an HT16K33 LED driver and log keyscan events. 10 This sample controls the LEDs connected to a `Holtek HT16K33`_ 11 driver. The sample supports up to 128 LEDs connected to the 14 The LEDs are controlled using the following pattern: 16 1. turn on all connected (up to 128) LEDs one-by-one 17 2. blink the LEDs at 2 Hz, 1 Hz, and 0.5 Hz 19 4. turn off all LEDs, restore 100% brightness, and start over
|
/Zephyr-Core-3.5.0/dts/bindings/led/ |
D | gpio-leds.yaml | 5 This allows you to define a group of LEDs. Each LED in the group is 7 gpio-leds node. 9 Here is an example which defines three LEDs in the node /leds: 12 leds { 13 compatible = "gpio-leds"; 35 compatible: "gpio-leds"
|
D | led-controller.yaml | 4 # Common fields for LED controllers and child LEDs 18 LEDs in an array/strip are not wired following the LED order of 27 For example the channel to color mapping of RGB LEDs would be
|
/Zephyr-Core-3.5.0/samples/drivers/led_pwm/boards/ |
D | mr_canhubk3.conf | 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-Core-3.5.0/samples/drivers/led_is31fl3216a/ |
D | README.rst | 5 Control up to 16 PWM LEDs connected to an IS31FL3216A driver chip. 10 This sample controls up to 16 LEDs connected to a is31fl3216a driver. 15 Once each LED was pulsed, multiple LEDs are pulse simultaneously using the 26 - Increase the luminosity of LEDs 2 to 4 until 100% is reached 27 - Decrease the luminosity of LEDs 2 to 4 until completely turned off 38 _is31fl3216a LED driver (with 16 LEDs wired) is connected to the I2C bus at
|
/Zephyr-Core-3.5.0/samples/drivers/led_pca9633/src/ |
D | main.c | 40 LOG_INF("Testing leds"); in main() 43 /* Turn on LEDs one by one */ in main() 53 /* Turn off LEDs one by one */ in main() 63 /* Set the brightness to half max of LEDs one by one */ in main() 73 /* Turn off LEDs one by one */ in main() 83 /* Test the blinking of LEDs one by one */ in main() 94 /* Wait a few blinking before turning off the LEDs */ in main() 97 /* Turn off LEDs one by one */ in main()
|
/Zephyr-Core-3.5.0/samples/drivers/led_apa102c_bitbang/src/ |
D | main.c | 16 * Protect your eyes and do not look directly into those LEDs. 47 /* Number of LEDS linked together */ 71 int leds = 0; in main() local 93 for (leds = 0; leds < NUM_LEDS; leds++) { in main() 94 send_rgb(gpio_dev, rgb[(idx + leds) % NUM_RGB]); in main() 97 /* If there are more LEDs linked together, in main()
|
/Zephyr-Core-3.5.0/samples/drivers/led_lp5569/ |
D | README.rst | 5 Control 9 LEDs connected to an LP5569 driver chip. 10 This sample controls 9 LEDs connected to an LP5569 driver. The sample turns 11 all LEDs on and switches all LEDs off again within a one second interval. 32 [00:00:00.361,694] <inf> app: Testing 9 LEDs ..
|
/Zephyr-Core-3.5.0/samples/subsys/modbus/tcp_server/ |
D | sample.yaml | 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")
|
/Zephyr-Core-3.5.0/samples/drivers/led_lp5569/src/ |
D | main.c | 34 * Display a continuous pattern that turns on 9 LEDs at 1 s one by in main() 35 * one until it reaches the end and turns off LEDs in reverse order. in main() 38 LOG_INF("Testing 9 LEDs .."); in main() 41 /* Turn on LEDs one by one */ in main() 51 /* Turn all LEDs off slowly to demonstrate set_brightness */ in main()
|
/Zephyr-Core-3.5.0/samples/drivers/led_lp50xx/ |
D | README.rst | 5 Control up to 12 RGB LEDs connected to an LP50xx driver chip. 10 This sample controls up to 12 LEDs connected to a LP50xx driver. 14 (described below) is applied to all the LEDs simultaneously (using the 21 For all the LEDs first (using channel API) and then for each LED one by one: 40 LED driver (with 10 LEDs wired) is connected to the I2C0 bus at address 0x30.
|
/Zephyr-Core-3.5.0/samples/basic/threads/ |
D | README.rst | 5 Spawn multiple threads that blink LEDs and print information to the console. 14 The first two each control an LED. These LEDs, ``led0`` and ``led1``, have 30 The board must have two LEDs connected via GPIO pins. These are called "User 31 LEDs" on many of Zephyr's :ref:`boards`. The LEDs must be configured using the
|
/Zephyr-Core-3.5.0/boards/arm/rpi_pico/ |
D | rpi_pico.dts | 12 leds { 13 compatible = "gpio-leds"; 21 compatible = "pwm-leds";
|
/Zephyr-Core-3.5.0/boards/arm/nucleo_l452re/ |
D | nucleo_l452re_p.dts | 17 leds: leds { label 18 compatible = "gpio-leds";
|
D | nucleo_l452re.dts | 18 leds: leds { label 19 compatible = "gpio-leds";
|
/Zephyr-Core-3.5.0/samples/drivers/led_is31fl3733/ |
D | README.rst | 5 Control a matrix of up to 192 LEDs connected to an IS31FL3733 driver chip. 10 This sample controls a matrix of up to 192 LEDs. The sample performs the 13 - Set all LEDs to full brightness with :c:func:`led_write_channels` API 23 The number of LEDs can be limited using the following sample specific Kconfigs:
|
/Zephyr-Core-3.5.0/drivers/led/ |
D | lp3943.c | 15 * registers. This driver partitions the available LEDs into two groups as 16 * 0 to 7 and 8 to 15 and assigns PSC0/PWM0 to LEDs from 0 to 7 and PSC1/PWM1 17 * to LEDs from 8 to 15. So, it is not possible to set unique blink period 18 * and brightness value for LEDs in a group, changing either of these 19 * values for a LED will affect other LEDs also. 115 /* Set DIMx states for the LEDs */ in lp3943_set_dim_states() 141 /* Use DIM0 for LEDs 0 to 7 and DIM1 for LEDs 8 to 15 */ in lp3943_led_blink() 182 /* Use DIM0 for LEDs 0 to 7 and DIM1 for LEDs 8 to 15 */ in lp3943_led_set_brightness()
|
/Zephyr-Core-3.5.0/samples/drivers/led_lp3943/src/ |
D | main.c | 37 * Display a continuous pattern that turns on 16 LEDs at 1s one by in main() 38 * one until it reaches the end and turns off LEDs in reverse order. in main() 44 /* Turn on LEDs one by one */ in main() 54 /* Turn off LEDs one by one */ in main()
|
/Zephyr-Core-3.5.0/boards/arm/nucleo_h745zi_q/ |
D | nucleo_h745zi_q.dtsi | 12 leds: leds { label 13 compatible = "gpio-leds";
|
/Zephyr-Core-3.5.0/tests/drivers/gpio/gpio_get_direction/boards/ |
D | nrf52_bsim.overlay | 13 leds { 14 compatible = "gpio-leds";
|
/Zephyr-Core-3.5.0/samples/basic/blinky/ |
D | README.rst | 28 #. Have an LED connected via a GPIO pin (these are called "User LEDs" on many of 71 leds { 72 compatible = "gpio-leds"; 85 - See :dtcompatible:`gpio-leds` for more information on defining GPIO-based LEDs
|