From: Dan Murphy <dmurphy@ti.com>
To: jacek.anaszewski@gmail.com, pavel@ucw.cz
Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
Dan Murphy <dmurphy@ti.com>
Subject: [PATCH v5 0/2] Multicolor Documentation update
Date: Mon, 1 Jul 2019 15:46:32 -0500 [thread overview]
Message-ID: <20190701204634.10517-1-dmurphy@ti.com> (raw)
Hello
After some off line conversations with the LED maintainers I update the
documentation for the multicolor framework with what I hope to be a good
compromise.
I have add the "color_mix" (name is not set but could not think of a better one)
file for writing the monochrome LEDs as a group. Also I have added a "color_id"
file for each monochrome LED as read only so that the LED indexes in the array
are known when writing to the color_mix file. This will help in determining the
order of the LEDs in the array.
I am not carrying any RoB/SoB in this patchset as these interfaces are changing.
Dan
Dan Murphy (2):
leds: multicolor: Add sysfs interface definition
documention: leds: Add multicolor class documentation
.../ABI/testing/sysfs-class-led-multicolor | 67 ++++++++
Documentation/leds/leds-class-multicolor.txt | 145 ++++++++++++++++++
2 files changed, 212 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-class-led-multicolor
create mode 100644 Documentation/leds/leds-class-multicolor.txt
--
2.22.0.214.g8dca754b1e
next reply other threads:[~2019-07-01 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 20:46 Dan Murphy [this message]
2019-07-01 20:46 ` [PATCH v5 1/2] leds: multicolor: Add sysfs interface definition Dan Murphy
2019-07-01 20:46 ` [PATCH v5 2/2] documention: leds: Add multicolor class documentation Dan Murphy
2019-07-16 19:18 ` Jacek Anaszewski
2019-07-16 19:27 ` Dan Murphy
2019-07-16 20:37 ` 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=20190701204634.10517-1-dmurphy@ti.com \
--to=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).