OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/samples/drivers/led_ws2812/boards/bbc_microbit.overlay

27 lines
481 B
Plaintext
Raw Normal View History

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-07 01:28:54 +08:00
/*
* Copyright (c) 2019, Nordic Semiconductor ASA
*
* SPDX-License-Identifier: Apache-2.0
*/
#include <dt-bindings/gpio/gpio.h>
led_strip: ws2812: allow to configure channel mapping Some devices compatibles with the WS2812 IC have a different channel to color mappings (e.g. RGB, BGR, RGBW, etc). This patch introduces the "color-mapping" required property for the WS2812 DT binding and adds support to the ws2812_gpio and ws2812_spi drivers. This new property allows to configure the color to channel mapping of a WS2812 compatible LED strip controller from its DT node. Since this property also allows to know if a white channel is available, then this patch removes the "has-white-channel" property. Signed-off-by: Simon Guinot <simon.guinot@seagate.com>
2021-05-18 01:22:36 +08:00
#include <dt-bindings/led/led.h>
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-07 01:28:54 +08:00
/ {
led_strip: ws2812 {
compatible = "worldsemi,ws2812-gpio";
label = "WS2812";
chain-length = <16>; /* arbitrary; change at will */
led_strip: ws2812: allow to configure channel mapping Some devices compatibles with the WS2812 IC have a different channel to color mappings (e.g. RGB, BGR, RGBW, etc). This patch introduces the "color-mapping" required property for the WS2812 DT binding and adds support to the ws2812_gpio and ws2812_spi drivers. This new property allows to configure the color to channel mapping of a WS2812 compatible LED strip controller from its DT node. Since this property also allows to know if a white channel is available, then this patch removes the "has-white-channel" property. Signed-off-by: Simon Guinot <simon.guinot@seagate.com>
2021-05-18 01:22:36 +08:00
color-mapping = <LED_COLOR_ID_GREEN
LED_COLOR_ID_RED
LED_COLOR_ID_BLUE>;
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-07 01:28:54 +08:00
/* P0: */
in-gpios = <&gpio0 3 0>;
};
aliases {
led-strip = &led_strip;
};
};