From: David Lechner <david@lechnology.com>
To: Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: David Lechner <david@lechnology.com>,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
Marcel Holtmann <marcel@holtmann.org>,
Pavel Machek <pavel@ucw.cz>
Subject: [PATCH v4 0/3] leds: Introduce userspace leds driver
Date: Fri, 16 Sep 2016 14:16:47 -0500 [thread overview]
Message-ID: <1474053410-24387-1-git-send-email-david@lechnology.com> (raw)
v2 changes:
* sort #includes
* fix typo in Kconfig
* Add Documentation text file
v3 changes:
* fix typos in docs
* rename "leds class" to "LED class" in docs
* rebase on linux-leds/for-next
v4 changes:
* Use devm_led_classdev_register() instead of led_classdev_register()
* Clarified how to create multiple devices in documentation
* uledmon.c now uses blocking reads instead of poll()
* Add some sanity checking on user-provided device name to make sure it is not
a directory name
* Reading from /dev/uleds allows any size read buffer - still only returns one
byte regardless of size
* Reading from /dev/uleds blocks until the brightness is changed
* LEDS_MAX_NAME_SIZE is reduced to 64 to match existing name size limit
* New patch to use LEDS_MAX_NAME_SIZE in drivers/leds/led-class.c
* Moved example code to tool/leds/uledmon.c (new patch with Makefile)
David Lechner (3):
leds: Introduce userspace leds driver
leds: Use macro for max device node name size
tools/leds: Add uledmon program for monitoring userspace LEDs
Documentation/leds/uleds.txt | 36 +++++++
drivers/leds/Kconfig | 8 ++
drivers/leds/Makefile | 3 +
drivers/leds/led-class.c | 3 +-
drivers/leds/uleds.c | 230 +++++++++++++++++++++++++++++++++++++++++++
include/uapi/linux/Kbuild | 1 +
include/uapi/linux/uleds.h | 23 +++++
tools/Makefile | 7 +-
tools/leds/.gitignore | 1 +
tools/leds/Makefile | 13 +++
tools/leds/uledmon.c | 62 ++++++++++++
11 files changed, 383 insertions(+), 4 deletions(-)
create mode 100644 Documentation/leds/uleds.txt
create mode 100644 drivers/leds/uleds.c
create mode 100644 include/uapi/linux/uleds.h
create mode 100644 tools/leds/.gitignore
create mode 100644 tools/leds/Makefile
create mode 100644 tools/leds/uledmon.c
--
2.7.4
next reply other threads:[~2016-09-16 19:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20160916191750eucas1p2437e0fa04cc99964b79cb774ef482e5a@eucas1p2.samsung.com>
2016-09-16 19:16 ` David Lechner [this message]
2016-09-16 19:16 ` [PATCH v4 1/3] leds: Introduce userspace leds driver David Lechner
2016-09-22 13:43 ` Linus Walleij
2016-09-22 13:44 ` Linus Walleij
2016-09-22 16:45 ` David Lechner
2016-09-24 12:06 ` Pavel Machek
2016-11-08 11:26 ` Jacek Anaszewski
2016-11-08 19:08 ` David Lechner
2016-11-08 20:29 ` Jacek Anaszewski
2016-11-09 7:05 ` Pavel Machek
2016-11-09 8:44 ` Jacek Anaszewski
2016-09-16 19:16 ` [PATCH v4 2/3] leds: Use macro for max device node name size David Lechner
2016-09-16 19:16 ` [PATCH v4 3/3] tools/leds: Add uledmon program for monitoring userspace LEDs David Lechner
2016-09-20 8:56 ` [PATCH v4 0/3] leds: Introduce userspace leds driver Jacek Anaszewski
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=1474053410-24387-1-git-send-email-david@lechnology.com \
--to=david@lechnology.com \
--cc=j.anaszewski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
/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.