From: "Vesa Jääskeläinen" <dachaac@gmail.com>
To: Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>
Cc: robh+dt@kernel.org, jacek.anaszewski@gmail.com,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [RFC PATCH] leds: multicolor: Add sysfs interface definition
Date: Fri, 8 Feb 2019 07:09:14 +0200 [thread overview]
Message-ID: <6d50b09c-87be-d48f-cfe5-f5143c18d38c@gmail.com> (raw)
In-Reply-To: <6afa674b-9c4e-2568-c758-030e93aebd06@gmail.com>
Hi All,
On 08/02/2019 6.55, Vesa Jääskeläinen wrote:
> Hi All,
>
> On 31/01/2019 0.35, Pavel Machek wrote:
>> On Wed 2019-01-30 12:30:05, Dan Murphy wrote:
>>> Add a documentation of LED Multicolor LED class specific
>>> sysfs attributes.
>>
>> No, sorry. This does not most of the requirements.
>>
>> Pavel
>>
>> Requirements for RGB LED interface:
>
> ...
>
> I have tried to capture relevant parts of ideas and requirements and
> usage in a wiki page in github:
>
> https://github.com/vesajaaskelainen/linux-multicolor-leds/wiki
>
> I believe the discussion is good to perform in mailing list -- I am
> happy to update or give you access to update the wiki so we could have
> easy to use summary/details source during discussions.
>
> Ideas on the interface seem to be a bit drifting so I apologize if some
> of Your ideas were not captured.
>
> There has been at least two direct proposals for userspace interface and
> I tried to provide usage example also for Dan's proposal. Feel free to
> correct me if I made a mistake.
>
> I believe it is a good to create summary page as there seems to many
> aspects to be though out. What do you feel on this approach?
And should we perhaps move this discussion only to linux-leds mailing
list for successive replies :) ? So we don't generate too broad traffic.
Thanks,
Vesa Jääskeläinen
next prev parent reply other threads:[~2019-02-08 5:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 18:30 Dan Murphy
2019-01-30 19:37 ` Jacek Anaszewski
2019-01-30 19:59 ` Dan Murphy
2019-01-30 20:20 ` Jacek Anaszewski
2019-01-30 21:07 ` Dan Murphy
2019-01-30 22:14 ` Jacek Anaszewski
2019-01-31 13:48 ` Dan Murphy
2019-01-31 20:54 ` Jacek Anaszewski
2019-01-30 22:35 ` Pavel Machek
2019-02-08 4:55 ` Vesa Jääskeläinen
2019-02-08 5:09 ` Vesa Jääskeläinen [this message]
2019-02-08 16:55 ` Dan Murphy
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=6d50b09c-87be-d48f-cfe5-f5143c18d38c@gmail.com \
--to=dachaac@gmail.com \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
/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
all inboxes | Powered by JetHome®