From: Pavel Machek <pavel@ucw.cz>
To: "Michał Kępień" <kernel@kempniu.pl>
Cc: Jonathan Woithe <jwoithe@just42.net>,
Darren Hart <dvhart@infradead.org>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fujitsu-laptop: Support radio LED
Date: Thu, 14 Apr 2016 14:39:38 +0200 [thread overview]
Message-ID: <20160414123938.GA13049@amd> (raw)
In-Reply-To: <20160412122615.GB2583@eudyptula.hq.kempniu.pl>
Hi!
>
> Either your clock is really off or it took you 3 weeks to get this
> message out ;) Just letting you know.
Clock is off.
> > > +
> > > +static enum led_brightness radio_led_get(struct led_classdev *cdev);
> > > +static void radio_led_set(struct led_classdev *cdev,
> > > + enum led_brightness brightness);
> > > +
> > > +static struct led_classdev radio_led = {
> > > + .name = "fujitsu::radio_led",
> > > + .brightness_get = radio_led_get,
> > > + .brightness_set = radio_led_set
> > > +};
> >
> > Is the naming consistent with other drivers?
>
> I am not entirely clear what you are referring to. If it is the double
> colon, that seems to be the convention used throughout the
> platform-driver-x86 tree. If it is the LED's name ("radio_led"), I
> failed to find a similarly purposed LED in the platform-driver-x86 tree
> with a name I could reuse. I decided to use the _led suffix to
> differentiate this LED from the "lamps" already implemented by
> fujitsu-laptop.
I'd expected the led to be called "fujitsu::rfkill" but it looks that you
are first one in tree with something similar, so I guess you get to
pick the name.
It would be nice to have easily-available list of all the suffixes. We
have keyboard backlights, keyboard frontlights, LED flashes, ...
> > Should there be default trigger so that it works out of the box?
>
> I have covered this issue in the lengthy comment attached to this patch:
>
> > One last remark is that I think this LED would best be driven by an
> > inverted airplane mode LED trigger (as proposed by João Paulo Rechi
> > Vita). As the code for that trigger is not yet merged, I refrained from
> > setting the default_trigger field in struct led_classdev radio_led.
> > Perhaps it's a candidate for a follow-up patch in the future.
>
> I haven't found a way to make this work the intended way out of the box,
> not with the currently available set of LED triggers. That being said,
> I would be happy if someone proved me wrong.
Aha, ok.
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2016-04-14 12:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 11:28 [PATCH] fujitsu-laptop: Support radio LED Michał Kępień
2016-03-18 12:04 ` Jonathan Woithe
2016-03-22 13:30 ` Michał Kępień
2016-03-23 7:51 ` Michał Kępień
2016-03-24 11:35 ` Jonathan Woithe
2016-04-10 2:30 ` Darren Hart
2016-04-10 10:52 ` Jonathan Woithe
2016-04-12 12:03 ` Michał Kępień
2016-04-12 12:49 ` Jonathan Woithe
2016-04-12 13:29 ` Michał Kępień
2016-04-12 12:36 ` Jonathan Woithe
2016-04-15 4:42 ` Darren Hart
2016-04-15 5:33 ` Jonathan Woithe
2016-04-15 5:44 ` Darren Hart
2016-04-15 6:00 ` Jonathan Woithe
2016-04-15 7:32 ` Darren Hart
2016-03-28 17:44 ` Darren Hart
2016-03-22 11:27 ` Pavel Machek
2016-04-12 12:26 ` Michał Kępień
2016-04-14 12:39 ` Pavel Machek [this message]
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=20160414123938.GA13049@amd \
--to=pavel@ucw.cz \
--cc=dvhart@infradead.org \
--cc=jwoithe@just42.net \
--cc=kernel@kempniu.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.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