michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/drivers/led_strip/Kconfig.ws2812

103 lines
3.9 KiB
Text
Raw Permalink Normal View History

drivers: led_strip: add WS2812-ish driver The WS2812 LED driver IC has a one-wire interface which encodes bit values as pulse widths. The ICs themselves are basically shift registers. Roughly speaking, a "short" pulse shifts in a zero bit, a "long" pulse shifts in a one bit, and an inter-pulse gap exceeding a reset time threshold causes a pixel to latch the shifted-in color values. Each chip has an output pin for daisy chaining. Refer to the chip datsheets and comments in Kconfig.ws2812 for more details. To meet timing without hogging the core, this driver generates pulses using SPI. To work, this requires the MOSI line to stay low between SPI frames, and for inter-frame delays to be less than the reset pulse time. There are other ways do it (PWM + DMA on some SoCs, GPIO bit-banging if no other tasks need the core), but this is a reasonably general-purpose implementation. Signed-off-by: Marti Bolivar <marti.bolivar@linaro.org>
2017-10-16 23:28:15 -04:00
# Copyright (c) 2017 Linaro Limited
drivers: led_strip: modernize and fix up ws2812 drivers/sample Convert the GPIO based driver to the new GPIO API. (Only the gpio_configure() call is affected). Move configuration to DT where appropriate for both SPI and GPIO drivers, only leaving the SPI vs. GPIO decision in Kconfig (in addition to the basic enable for the driver.) Move some files around to clean up as a result of this change. led_ws2812 sample changes: - make the pattern easier to look at by emitting less light - use led_strip alias from DT to get strip device, allocate appropriate struct led_rgb buffer, etc. - move the pins around and remove 96b_carbon support (I have no board to test with) GPIO driver specific changes: - str is required to write OUTSET/OUTCLR, not strb. The registers are word-sized. - the str[b] registers must all be in r0-r7, so "l" is the correct GCC inline assembly constraint for both "base" and "pin" SPI driver specific changes: - match the GPIO driver in not supporting the update_channels API method, which never made sense for this type of strip - return -ENOMEM when the user tries to send more pixel data than we have buffer space for instead of -EINVAL Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2019-11-06 09:28:54 -08:00
# Copyright (c) 2019 Nordic Semiconductor ASA
#
drivers: led_strip: add WS2812-ish driver The WS2812 LED driver IC has a one-wire interface which encodes bit values as pulse widths. The ICs themselves are basically shift registers. Roughly speaking, a "short" pulse shifts in a zero bit, a "long" pulse shifts in a one bit, and an inter-pulse gap exceeding a reset time threshold causes a pixel to latch the shifted-in color values. Each chip has an output pin for daisy chaining. Refer to the chip datsheets and comments in Kconfig.ws2812 for more details. To meet timing without hogging the core, this driver generates pulses using SPI. To work, this requires the MOSI line to stay low between SPI frames, and for inter-frame delays to be less than the reset pulse time. There are other ways do it (PWM + DMA on some SoCs, GPIO bit-banging if no other tasks need the core), but this is a reasonably general-purpose implementation. Signed-off-by: Marti Bolivar <marti.bolivar@linaro.org>
2017-10-16 23:28:15 -04:00
# SPDX-License-Identifier: Apache-2.0
# The following blog post is an excellent resource about pulse timing:
#
# https://wp.josh.com/2014/05/13/ws2812-neopixels-are-not-so-finicky-once-you-get-to-know-them/
drivers: led_strip: modernize and fix up ws2812 drivers/sample Convert the GPIO based driver to the new GPIO API. (Only the gpio_configure() call is affected). Move configuration to DT where appropriate for both SPI and GPIO drivers, only leaving the SPI vs. GPIO decision in Kconfig (in addition to the basic enable for the driver.) Move some files around to clean up as a result of this change. led_ws2812 sample changes: - make the pattern easier to look at by emitting less light - use led_strip alias from DT to get strip device, allocate appropriate struct led_rgb buffer, etc. - move the pins around and remove 96b_carbon support (I have no board to test with) GPIO driver specific changes: - str is required to write OUTSET/OUTCLR, not strb. The registers are word-sized. - the str[b] registers must all be in r0-r7, so "l" is the correct GCC inline assembly constraint for both "base" and "pin" SPI driver specific changes: - match the GPIO driver in not supporting the update_channels API method, which never made sense for this type of strip - return -ENOMEM when the user tries to send more pixel data than we have buffer space for instead of -EINVAL Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2019-11-06 09:28:54 -08:00
config WS2812_STRIP_SPI
drivers: led_strip: Enabling config with DT_HAS_.. Applying the modern way which is adding `default y` and `depends on DT_HAS_...` to enable configs. Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com>
2024-03-12 09:37:33 +09:00
bool "WS2812 LED strip SPI driver"
default y
depends on DT_HAS_WORLDSEMI_WS2812_SPI_ENABLED
drivers: led_strip: ws2812: Remove WS2812_STRIP and WS2812_STRIP_DRIVER Removing `choice WS2812_STRIP_DRIVER` to enable the use of multiple types of WS2812 drivers. Also, `menuconfig WS2812_STRIP` will be deleted as it does not correspond to the appropriate settings. Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com>
2024-03-09 21:50:36 +09:00
select SPI if $(dt_compat_on_bus,$(DT_COMPAT_WORLDSEMI_WS2812_SPI),spi)
drivers: led_strip: add WS2812-ish driver The WS2812 LED driver IC has a one-wire interface which encodes bit values as pulse widths. The ICs themselves are basically shift registers. Roughly speaking, a "short" pulse shifts in a zero bit, a "long" pulse shifts in a one bit, and an inter-pulse gap exceeding a reset time threshold causes a pixel to latch the shifted-in color values. Each chip has an output pin for daisy chaining. Refer to the chip datsheets and comments in Kconfig.ws2812 for more details. To meet timing without hogging the core, this driver generates pulses using SPI. To work, this requires the MOSI line to stay low between SPI frames, and for inter-frame delays to be less than the reset pulse time. There are other ways do it (PWM + DMA on some SoCs, GPIO bit-banging if no other tasks need the core), but this is a reasonably general-purpose implementation. Signed-off-by: Marti Bolivar <marti.bolivar@linaro.org>
2017-10-16 23:28:15 -04:00
help
drivers: led_strip: Enabling config with DT_HAS_.. Applying the modern way which is adding `default y` and `depends on DT_HAS_...` to enable configs. Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com>
2024-03-12 09:37:33 +09:00
Enable driver for WS2812 (and compatibles) LED strip using SPI.
drivers: led_strip: modernize and fix up ws2812 drivers/sample Convert the GPIO based driver to the new GPIO API. (Only the gpio_configure() call is affected). Move configuration to DT where appropriate for both SPI and GPIO drivers, only leaving the SPI vs. GPIO decision in Kconfig (in addition to the basic enable for the driver.) Move some files around to clean up as a result of this change. led_ws2812 sample changes: - make the pattern easier to look at by emitting less light - use led_strip alias from DT to get strip device, allocate appropriate struct led_rgb buffer, etc. - move the pins around and remove 96b_carbon support (I have no board to test with) GPIO driver specific changes: - str is required to write OUTSET/OUTCLR, not strb. The registers are word-sized. - the str[b] registers must all be in r0-r7, so "l" is the correct GCC inline assembly constraint for both "base" and "pin" SPI driver specific changes: - match the GPIO driver in not supporting the update_channels API method, which never made sense for this type of strip - return -ENOMEM when the user tries to send more pixel data than we have buffer space for instead of -EINVAL Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2019-11-06 09:28:54 -08:00
The SPI driver is portable, but requires significantly more
memory (1 byte of overhead per bit of pixel data).
drivers: led_strip: add WS2812-ish driver The WS2812 LED driver IC has a one-wire interface which encodes bit values as pulse widths. The ICs themselves are basically shift registers. Roughly speaking, a "short" pulse shifts in a zero bit, a "long" pulse shifts in a one bit, and an inter-pulse gap exceeding a reset time threshold causes a pixel to latch the shifted-in color values. Each chip has an output pin for daisy chaining. Refer to the chip datsheets and comments in Kconfig.ws2812 for more details. To meet timing without hogging the core, this driver generates pulses using SPI. To work, this requires the MOSI line to stay low between SPI frames, and for inter-frame delays to be less than the reset pulse time. There are other ways do it (PWM + DMA on some SoCs, GPIO bit-banging if no other tasks need the core), but this is a reasonably general-purpose implementation. Signed-off-by: Marti Bolivar <marti.bolivar@linaro.org>
2017-10-16 23:28:15 -04:00
drivers: led_strip: add WS2812 I2S-based driver Add a driver implementation that uses the I2S peripheral. Based off this blog post: https://electronut.in/nrf52-i2s-ws2812/ Should help with #33505, #29877 and maybe #47780, as there is no garbage data at the end of transmissions on nRF52832, and no gaps. Signed-off-by: Jonathan Rico <jonathan@rico.live>
2022-11-07 21:42:43 +01:00
config WS2812_STRIP_I2S
drivers: led_strip: Enabling config with DT_HAS_.. Applying the modern way which is adding `default y` and `depends on DT_HAS_...` to enable configs. Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com>
2024-03-12 09:37:33 +09:00
bool "WS2812 LED strip I2S driver"
default y
depends on DT_HAS_WORLDSEMI_WS2812_I2S_ENABLED
drivers: led_strip: ws2812: Remove WS2812_STRIP and WS2812_STRIP_DRIVER Removing `choice WS2812_STRIP_DRIVER` to enable the use of multiple types of WS2812 drivers. Also, `menuconfig WS2812_STRIP` will be deleted as it does not correspond to the appropriate settings. Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com>
2024-03-09 21:50:36 +09:00
select I2S if $(dt_compat_on_bus,$(DT_COMPAT_WORLDSEMI_WS2812_I2S),i2s)
drivers: led_strip: add WS2812 I2S-based driver Add a driver implementation that uses the I2S peripheral. Based off this blog post: https://electronut.in/nrf52-i2s-ws2812/ Should help with #33505, #29877 and maybe #47780, as there is no garbage data at the end of transmissions on nRF52832, and no gaps. Signed-off-by: Jonathan Rico <jonathan@rico.live>
2022-11-07 21:42:43 +01:00
help
drivers: led_strip: Enabling config with DT_HAS_.. Applying the modern way which is adding `default y` and `depends on DT_HAS_...` to enable configs. Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com>
2024-03-12 09:37:33 +09:00
Enable driver for WS2812 (and compatibles) LED strip using I2S.
drivers: led_strip: add WS2812 I2S-based driver Add a driver implementation that uses the I2S peripheral. Based off this blog post: https://electronut.in/nrf52-i2s-ws2812/ Should help with #33505, #29877 and maybe #47780, as there is no garbage data at the end of transmissions on nRF52832, and no gaps. Signed-off-by: Jonathan Rico <jonathan@rico.live>
2022-11-07 21:42:43 +01:00
Uses the I2S peripheral, memory usage is 4 bytes per color,
times the number of pixels. A few more for the start and end
delay. The reset delay has a coarse resolution of ~20us.
drivers: led_strip: modernize and fix up ws2812 drivers/sample Convert the GPIO based driver to the new GPIO API. (Only the gpio_configure() call is affected). Move configuration to DT where appropriate for both SPI and GPIO drivers, only leaving the SPI vs. GPIO decision in Kconfig (in addition to the basic enable for the driver.) Move some files around to clean up as a result of this change. led_ws2812 sample changes: - make the pattern easier to look at by emitting less light - use led_strip alias from DT to get strip device, allocate appropriate struct led_rgb buffer, etc. - move the pins around and remove 96b_carbon support (I have no board to test with) GPIO driver specific changes: - str is required to write OUTSET/OUTCLR, not strb. The registers are word-sized. - the str[b] registers must all be in r0-r7, so "l" is the correct GCC inline assembly constraint for both "base" and "pin" SPI driver specific changes: - match the GPIO driver in not supporting the update_channels API method, which never made sense for this type of strip - return -ENOMEM when the user tries to send more pixel data than we have buffer space for instead of -EINVAL Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2019-11-06 09:28:54 -08:00
config WS2812_STRIP_GPIO
drivers: led_strip: Enabling config with DT_HAS_.. Applying the modern way which is adding `default y` and `depends on DT_HAS_...` to enable configs. Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com>
2024-03-12 09:37:33 +09:00
bool "WS2812 LED strip GPIO driver"
drivers: ws2812_gpio: Make timing configurable and less hardware dependend The current driver contains assembly code which is specific for the nRF51 SOC which makes it incompatible with other SOC's. This patch adds support for other nRF SOC's as well. The timing is calucated based on the CPU clock frequency, but can be configured manually as well if needed. Changes have been verified on a Adafruit Feather nRF52840 Express board, which contains a single NeoPixel RGB LED. Timings have been verified using a scope connected to the WS1812 data line. Signed-off-by: Chaim Zax <chaim.zax@zaxx.pro>
2024-04-28 13:27:44 +02:00
# Only an Cortex-M inline assembly implementation for the nRF91, nRF51,
# nRF52 and nRF53 is supported currently.
drivers: led_strip: Enabling config with DT_HAS_.. Applying the modern way which is adding `default y` and `depends on DT_HAS_...` to enable configs. Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com>
2024-03-12 09:37:33 +09:00
default y
depends on DT_HAS_WORLDSEMI_WS2812_GPIO_ENABLED
drivers: ws2812_gpio: Make timing configurable and less hardware dependend The current driver contains assembly code which is specific for the nRF51 SOC which makes it incompatible with other SOC's. This patch adds support for other nRF SOC's as well. The timing is calucated based on the CPU clock frequency, but can be configured manually as well if needed. Changes have been verified on a Adafruit Feather nRF52840 Express board, which contains a single NeoPixel RGB LED. Timings have been verified using a scope connected to the WS1812 data line. Signed-off-by: Chaim Zax <chaim.zax@zaxx.pro>
2024-04-28 13:27:44 +02:00
depends on (SOC_SERIES_NRF91X || SOC_SERIES_NRF51X || SOC_SERIES_NRF52X || SOC_SERIES_NRF53X)
drivers: led_strip: ws2812: Remove scratch selection for non-GPIO The WS2812 LED strip driver does not use a scratch byte, therefore free up a byte per pixel which was unused except in the GPIO-based driver whereby it is used Signed-off-by: Jamie McCrae <spam@helper3000.net>
2023-10-28 18:55:41 +01:00
select LED_STRIP_RGB_SCRATCH
drivers: led_strip: add WS2812-ish driver The WS2812 LED driver IC has a one-wire interface which encodes bit values as pulse widths. The ICs themselves are basically shift registers. Roughly speaking, a "short" pulse shifts in a zero bit, a "long" pulse shifts in a one bit, and an inter-pulse gap exceeding a reset time threshold causes a pixel to latch the shifted-in color values. Each chip has an output pin for daisy chaining. Refer to the chip datsheets and comments in Kconfig.ws2812 for more details. To meet timing without hogging the core, this driver generates pulses using SPI. To work, this requires the MOSI line to stay low between SPI frames, and for inter-frame delays to be less than the reset pulse time. There are other ways do it (PWM + DMA on some SoCs, GPIO bit-banging if no other tasks need the core), but this is a reasonably general-purpose implementation. Signed-off-by: Marti Bolivar <marti.bolivar@linaro.org>
2017-10-16 23:28:15 -04:00
help
drivers: ws2812_gpio: Make timing configurable and less hardware dependend The current driver contains assembly code which is specific for the nRF51 SOC which makes it incompatible with other SOC's. This patch adds support for other nRF SOC's as well. The timing is calucated based on the CPU clock frequency, but can be configured manually as well if needed. Changes have been verified on a Adafruit Feather nRF52840 Express board, which contains a single NeoPixel RGB LED. Timings have been verified using a scope connected to the WS1812 data line. Signed-off-by: Chaim Zax <chaim.zax@zaxx.pro>
2024-04-28 13:27:44 +02:00
Enable driver for WS2812 (and compatibles) LED strip directly
controlling with GPIO. The GPIO driver does bit-banging with inline
assembly, and is not available on all SoCs.
drivers: led_strip: add WS2812-ish driver The WS2812 LED driver IC has a one-wire interface which encodes bit values as pulse widths. The ICs themselves are basically shift registers. Roughly speaking, a "short" pulse shifts in a zero bit, a "long" pulse shifts in a one bit, and an inter-pulse gap exceeding a reset time threshold causes a pixel to latch the shifted-in color values. Each chip has an output pin for daisy chaining. Refer to the chip datsheets and comments in Kconfig.ws2812 for more details. To meet timing without hogging the core, this driver generates pulses using SPI. To work, this requires the MOSI line to stay low between SPI frames, and for inter-frame delays to be less than the reset pulse time. There are other ways do it (PWM + DMA on some SoCs, GPIO bit-banging if no other tasks need the core), but this is a reasonably general-purpose implementation. Signed-off-by: Marti Bolivar <marti.bolivar@linaro.org>
2017-10-16 23:28:15 -04:00
led_strip: ws2812: claim compatibility with Everlight B1414 This patch states that the Everlight B1414 LED controller is compatible with the Worldsemi WS2812. Some information about it is added to the WS2812 DT binding and driver Kconfig files. Signed-off-by: Simon Guinot <simon.guinot@seagate.com>
2021-05-19 12:19:38 +02:00
Note that this driver is not compatible with the Everlight B1414
controller.
drivers: ws2812_gpio: Make timing configurable and less hardware dependend The current driver contains assembly code which is specific for the nRF51 SOC which makes it incompatible with other SOC's. This patch adds support for other nRF SOC's as well. The timing is calucated based on the CPU clock frequency, but can be configured manually as well if needed. Changes have been verified on a Adafruit Feather nRF52840 Express board, which contains a single NeoPixel RGB LED. Timings have been verified using a scope connected to the WS1812 data line. Signed-off-by: Chaim Zax <chaim.zax@zaxx.pro>
2024-04-28 13:27:44 +02:00
if WS2812_STRIP_GPIO
DT_CHOSEN_LED_STRIP := zephyr,led-strip
DT_CHOSEN_LED_STRIP_PATH := $(dt_chosen_path,$(DT_CHOSEN_LED_STRIP))
config DELAY_T1H
int "Delay 1 bit high pulse"
default $(dt_node_int_prop_int,$(DT_CHOSEN_LED_STRIP_PATH),delay-t1h) \
if $(dt_node_has_prop,$(DT_CHOSEN_LED_STRIP_PATH),delay-t1h)
default $(div,$(mul,700,$(dt_node_int_prop_int,/cpus/cpu@0,clock-frequency)),1000000000) \
if $(dt_node_has_prop,/cpus/cpu@0,clock-frequency)
default 7
help
Number of NOP assembly operations to create a delay for a 1 bit, high voltage period (default 700 nsec)
config DELAY_T1L
int "Delay 1 bit low pulse"
default $(dt_node_int_prop_int,$(DT_CHOSEN_LED_STRIP_PATH),delay-t1l) \
if $(dt_node_has_prop,$(DT_CHOSEN_LED_STRIP_PATH),delay-t1l)
default $(div,$(mul,600,$(dt_node_int_prop_int,/cpus/cpu@0,clock-frequency)),1000000000) \
if $(dt_node_has_prop,/cpus/cpu@0,clock-frequency)
default 6
help
Number of NOP assembly operations to create a delay for a 1 bit, low voltage period (default 600 nsec)
config DELAY_T0H
int "Delay 0 bit high pulse"
default $(dt_node_int_prop_int,$(DT_CHOSEN_LED_STRIP_PATH),delay-t0h) \
if $(dt_node_has_prop,$(DT_CHOSEN_LED_STRIP_PATH),delay-t0h)
default $(div,$(mul,350,$(dt_node_int_prop_int,/cpus/cpu@0,clock-frequency)),1000000000) \
if $(dt_node_has_prop,/cpus/cpu@0,clock-frequency)
default 3
help
Number of NOP assembly operations to create a delay for a 0 bit, high voltage period (default 350 nsec)
config DELAY_T0L
int "Delay 0 bit low pulse"
default $(dt_node_int_prop_int,$(DT_CHOSEN_LED_STRIP_PATH),delay-t0l) \
if $(dt_node_has_prop,$(DT_CHOSEN_LED_STRIP_PATH),delay-t0l)
default $(div,$(mul,800,$(dt_node_int_prop_int,/cpus/cpu@0,clock-frequency)),1000000000) \
if $(dt_node_has_prop,/cpus/cpu@0,clock-frequency)
default 8
help
Number of NOP assembly operations to create a delay for a 0 bit, low voltage period (default 800 nsec)
endif
drivers: led_strip: add rpi_pico's PIO based ws2812 driver Add driver that based on RPI-PICO's PIO feature for ws2812. This driver can handle WS2812 or compatible LED strips. The single PIO node can handle up to 4 strips. Any pins that can be configured for PIO can be used for strips. I verified the samples/driver/led_ws2812 sample working with WS2812(144 pcs) led strip using following patches. - samples/drivers/led_ws2812/boards/rpi_pico.overlay ``` / { aliases { led-strip = &ws2812; }; }; &pinctrl { ws2812_pio0_default: ws2812_pio0_default { ws2812 { pinmux = <PIO0_P21>; }; }; }; &pio0 { status = "okay"; pio-ws2812 { compatible = "worldsemi,ws2812-rpi_pico-pio"; status = "okay"; pinctrl-0 = <&ws2812_pio0_default>; pinctrl-names = "default"; bit-waveform = <3>, <3>, <4>; ws2812: ws2812 { status = "okay"; output-pin = <21>; chain-length = <144>; color-mapping = <LED_COLOR_ID_GREEN LED_COLOR_ID_RED LED_COLOR_ID_BLUE>; reset-delay = <280>; frequency = <800000>; }; }; }; ``` - samples/drivers/led_ws2812/boards/rpi_pico.conf ``` CONFIG_WS2812_STRIP_RPI_PICO_PIO=y ``` Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com>
2023-02-25 09:00:59 +09:00
config WS2812_STRIP_RPI_PICO_PIO
drivers: led_strip: Enabling config with DT_HAS_.. Applying the modern way which is adding `default y` and `depends on DT_HAS_...` to enable configs. Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com>
2024-03-12 09:37:33 +09:00
bool "WS2812 LED strip Raspberry Pi Pico PIO driver"
default y
drivers: led_strip: add rpi_pico's PIO based ws2812 driver Add driver that based on RPI-PICO's PIO feature for ws2812. This driver can handle WS2812 or compatible LED strips. The single PIO node can handle up to 4 strips. Any pins that can be configured for PIO can be used for strips. I verified the samples/driver/led_ws2812 sample working with WS2812(144 pcs) led strip using following patches. - samples/drivers/led_ws2812/boards/rpi_pico.overlay ``` / { aliases { led-strip = &ws2812; }; }; &pinctrl { ws2812_pio0_default: ws2812_pio0_default { ws2812 { pinmux = <PIO0_P21>; }; }; }; &pio0 { status = "okay"; pio-ws2812 { compatible = "worldsemi,ws2812-rpi_pico-pio"; status = "okay"; pinctrl-0 = <&ws2812_pio0_default>; pinctrl-names = "default"; bit-waveform = <3>, <3>, <4>; ws2812: ws2812 { status = "okay"; output-pin = <21>; chain-length = <144>; color-mapping = <LED_COLOR_ID_GREEN LED_COLOR_ID_RED LED_COLOR_ID_BLUE>; reset-delay = <280>; frequency = <800000>; }; }; }; ``` - samples/drivers/led_ws2812/boards/rpi_pico.conf ``` CONFIG_WS2812_STRIP_RPI_PICO_PIO=y ``` Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com>
2023-02-25 09:00:59 +09:00
depends on DT_HAS_WORLDSEMI_WS2812_RPI_PICO_PIO_ENABLED
select PICOSDK_USE_PIO
help
drivers: led_strip: Enabling config with DT_HAS_.. Applying the modern way which is adding `default y` and `depends on DT_HAS_...` to enable configs. Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com>
2024-03-12 09:37:33 +09:00
Enable driver for WS2812 (and compatibles) LED strip using
docs: raspberrrypi: Correct names of products Replace occurrences of "RaspberryPi" with "Raspberry Pi" in documentation, comment blocks etc. Correct the name of "PicoW" to "Pico W", matching Raspberry Pi's documentation at https://www.raspberrypi.com/documentation/microcontrollers/pico-series.html . Signed-off-by: Andrew Featherstone <andrew.featherstone@gmail.com>
2025-03-30 22:25:21 +01:00
the Raspberry Pi Pico's PIO.
Copy permalink