summaryrefslogtreecommitdiffstats
path: root/drivers/led
Commit message (Collapse)AuthorAgeFilesLines
* dm: test: Add a test for the LED uclassSimon Glass2015-07-211-0/+6
| | | | | | Add a test to confirm that we can adjust LEDs using the led_gpio driver. Signed-off-by: Simon Glass <sjg@chromium.org>
* led: Return -ENODEV if the LED device cannot be foundSimon Glass2015-07-211-2/+3
| | | | | | | | | | We normally use -ENODEV for a missing device, rather than -ENOENT. The latter is reserved for when we have a device but cannot find something within it. Also avoid looking at the root LED device since it is only a container. Signed-off-by: Simon Glass <sjg@chromium.org>
* dm: led: Add a driver for GPIO-controlled LEDsSimon Glass2015-07-213-0/+111
| | | | | | | Add a simple driver which allows use of LEDs attached to GPIOs. The linux device tree binding is used. Signed-off-by: Simon Glass <sjg@chromium.org>
* dm: Add support for LEDsSimon Glass2015-07-213-0/+73
Add a simple uclass for LEDs, so that these can be controlled by the device tree and activated when needed. LEDs are referred to by their label. This implementation requires a driver for each type of LED (e.g GPIO, I2C). Signed-off-by: Simon Glass <sjg@chromium.org>
OpenPOWER on IntegriCloud