From: linux-kernel-dev at beckhoff.com <linux-kernel-dev@beckhoff.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 0/3] This series adds support for gpio-leds "default-state" property. The
Date: Wed, 4 Apr 2018 10:01:00 +0200 [thread overview]
Message-ID: <20180404080103.28033-1-linux-kernel-dev@beckhoff.com> (raw)
From: Patrick Bruenn <p.bruenn@beckhoff.com>
main usecase in mind are LEDs which indicate a state like "power on".
With this patchset applied, all you have to do is:
Add a gpio-led node with 'default-state = "on";' property to your device
tree. And the LED will automatically light up during U-Boot startup.
Changes in v3:
- use ofnode_read_bool() instead of ofnode_read_string() to determine if
LED node has the default-state property
Changes in v2:
- rebase to v2018.05-rc1
- add dm_test_led_default_state() to tests/dm/led.c
Patrick Bruenn (3):
dm: led: Support "default-state" property
dm: led: auto probe() LEDs with "default-state"
dm: led: add testcase for "default-state" property
arch/sandbox/dts/test.dts | 12 ++++++++++++
drivers/led/led_gpio.c | 25 ++++++++++++++++++++++++-
test/dm/led.c | 16 ++++++++++++++++
3 files changed, 52 insertions(+), 1 deletion(-)
--
2.11.0
next reply other threads:[~2018-04-04 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 8:01 linux-kernel-dev at beckhoff.com [this message]
2018-04-04 8:01 ` [U-Boot] [PATCH v3 1/3] dm: led: Support "default-state" property linux-kernel-dev at beckhoff.com
2018-04-08 13:55 ` Simon Glass
2018-04-04 8:01 ` [U-Boot] [PATCH v3 2/3] dm: led: auto probe() LEDs with "default-state" linux-kernel-dev at beckhoff.com
2018-04-08 13:55 ` Simon Glass
2018-04-04 8:01 ` [U-Boot] [PATCH v3 3/3] dm: led: add testcase for "default-state" property linux-kernel-dev at beckhoff.com
2018-04-08 13:55 ` Simon Glass
2018-04-10 16:22 ` [U-Boot] [U-Boot, v3, " Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180404080103.28033-1-linux-kernel-dev@beckhoff.com \
--to=linux-kernel-dev@beckhoff.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.