Thread (15 messages) read the whole thread 15 messages, 3 authors, 2016-06-21

Re: [RESEND PATCH 1/3] rfkill: Create "rfkill-airplane-mode" LED trigger

From: João Paulo Rechi Vita <jprvita@gmail.com>
Date: 2016-06-13 15:25:09
Also in: linux-api, lkml, netdev, platform-driver-x86

On 9 June 2016 at 08:43, Johannes Berg [off-list ref] wrote:
On Thu, 2016-05-19 at 09:16 +0200, Pavel Machek wrote:
(...)
quoted
LED
subsystem seems to use suffix of LED name to do that. So if we
standartize, lets say "::rfkill" suffix for this, it should work and
follow existing practice.
[...]
quoted
There is one -- suffix in the LED name.
I don't really think that's a good way, and it doesn't seem to be used
universally, but I suppose it's good enough.
The main practical drawback of this approach IMO is that we can't
guarantee that userspace processes will not step on each other's toes
trying to control the LED concurrently. But I guess that is something
that userspace will have to solve for now, I rather get this moving
without the trigger than not moving at all.
João, that means you should send a patch to add the ::rfkill suffix.
IMO "airplane" (or maybe "airplane-mode") is a better suffix, as it
reflects the label on the machine's chassis. I'll name it
"asus-wireless::airplane" and send this through platform-drivers-x86,
as this is now contained in the platform-drivers-x86 subsystem. Thanks
Johannes for your patience and help designing and reviewing the rfkill
changes, even if not all of them made it through in the end. And
thanks everyone else involved for the feedback.

Best regards,

--
João Paulo Rechi Vita
http://about.me/jprvita
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help