openwrt/upstream - upstream openwrt

diff options

author	Mathias Kresin <dev@kresin.me>	2017-10-15 12:29:22 +0200
committer	Mathias Kresin <dev@kresin.me>	2017-10-25 08:45:05 +0200
commit	1470c79cebdae83161a48a5e08c6002ecf090f42 (patch)
tree	cfd81b21e036ea69651028df67027bd79a5bd977 /scripts/cleanfile
parent	d456a888d07e97491ad2d57f470801bbbc4c06a6 (diff)
download	upstream-1470c79cebdae83161a48a5e08c6002ecf090f42.tar.gz upstream-1470c79cebdae83161a48a5e08c6002ecf090f42.tar.bz2 upstream-1470c79cebdae83161a48a5e08c6002ecf090f42.zip

ltq-adsl-app: use notification based ATM/PTM driver load

This patch removes the fixed atm/ptm driver loading and switches to notification based driver loading. Signed-off-by: Mathias Kresin <dev@kresin.me>

Diffstat (limited to 'scripts/cleanfile')

0 files changed, 0 insertions, 0 deletions

# RGB Lighting QMK has the ability to control RGB LEDs attached to your keyboard. This is commonly called *underglow*, due to the LEDs often being mounted on the bottom of the keyboard, producing a nice diffused effect when combined with a translucent case. ![Planck with RGB Underglow](https://raw.githubusercontent.com/qmk/qmk_firmware/3774a7fcdab5544fc787f4c200be05fcd417e31f/keyboards/planck/keymaps/yang/planck-with-rgb-underglow.jpg) Some keyboards come with RGB LEDs preinstalled. Others must have them installed after the fact. See the [Hardware Modification](#hardware-modification) section for information on adding RGB lighting to your keyboard. Currently QMK supports the following addressable LEDs on AVR microcontrollers (however, the white LED in RGBW variants is not supported): * WS2811, WS2812, WS2812B, WS2812C, etc. * SK6812, SK6812MINI, SK6805 These LEDs are called "addressable" because instead of using a wire per color, each LED contains a small microchip that understands a special protocol sent over a single wire. The chip passes on the remaining data to the next LED, allowing them to be chained together. In this way, you can easily control the color of the individual LEDs. ## Usage On keyboards with onboard RGB LEDs, it is usually enabled by default. If it is not working for you, check that your `rules.mk` includes the following: ```make RGBLIGHT_ENABLE = yes ``` At minimum you must define the data pin your LED strip is connected to, and the number of LEDs in the strip, in your `config.h`. If your keyboard has onboard RGB LEDs, and you are simply creating a keymap, you usually won't need to modify these. |Define |Description | |------------|---------------------------------------------| |`RGB_DI_PIN`|The pin connected to the data pin of the LEDs| |`RGBLED_NUM`|The number of LEDs connected | Then you should be able to use the keycodes below to change the RGB lighting to your liking. ### Color Selection QMK uses [Hue, Saturation, and Value](https://en.wikipedia.org/wiki/HSL_and_HSV) to select colors rather than RGB. The color wheel below demonstrates how this works. <img src="gitbook/images/color-wheel.svg" alt="HSV Color Wheel" width="250"/> Changing the **Hue** cycles around the circle. Changing the **Saturation** moves between the inner and outer sections of the wheel, affecting the intensity of the color.


context:
space:
mode: