From: "Guillaume Douézan-Grard" <gdouezangrard@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Andy Shevchenko <andy@infradead.org>,
Darren Hart <dvhart@infradead.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 4/4] platform/x86: topstar-laptop: add optional WLAN LED workaround
Date: Fri, 3 Nov 2017 16:07:35 +0100 [thread overview]
Message-ID: <20171103150735.GA13165@localhost> (raw)
In-Reply-To: <CAHp75VdN2PDDKsAM8qp1ssZB+K_zgwvJBKK7UEVvsSHV_cK73g@mail.gmail.com>
On Fri, Nov 03, 2017 at 02:50:52PM +0200, Andy Shevchenko wrote:
> On Sun, Oct 29, 2017 at 1:53 AM, Guillaume Douézan-Grard
> <gdouezangrard@gmail.com> wrote:
> > Topstar U931 laptops provide an LED synced with the WLAN adapter
> > hard-blocking state. Unfortunately, some models seem to be defective,
> > making impossible to hard-block the adapter with the WLAN switch and
> > thus the LED is useless.
> >
> > An ACPI method is available to programmatically control this switch and
> > it indirectly allows to control the LED.
> >
> > This commit registers the LED within the corresponding subsystem, making
> > possible for instance to use an rfkill-based trigger to synchronize the
> > LED with the soft-blocking state.
> >
> > This feature is disabled by default and can be enabled with the
> > `led_workaround` module parameter.
>
> > #include <linux/platform_device.h>
> > #include <linux/input.h>
> > #include <linux/input/sparse-keymap.h>
> > +#include <linux/leds.h>
>
> Yep, exact place, esp. after moving platform_device to the right place.
>
> > +static bool led_workaround;
> > +module_param_named(led_workaround, led_workaround, bool, 0444);
> > +MODULE_PARM_DESC(led_workaround,
> > + "Enables software-based WLAN LED control on systems with defective hardware switch");
>
> So, this is most problematic piece in the series.
>
> We are not encouraging module parameters. Why do we need one? Can't be
> detected automatically (perhaps based on DMI strings)?
Darren told me that. I tried to answer this question in the cover letter:
"These are barebone laptops, sold under quite a lot of brands and
configurations, with different firmwares and so on. I can only say for sure
that this issue is present for all the models sold under a specific brand,
that's why I'm reluctant to enable this by default with a DMI check."
In my case for instance, the DMI info has not been filled in by the retailler
since I only have the ODM base board information to identify a model.
> --
> With Best Regards,
> Andy Shevchenko
For now, I will prepare a new version containing the other needed changes you
pointed at for the other patches.
Thanks for your time,
--
Guillaume Douézan-Grard
next prev parent reply other threads:[~2017-11-03 15:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-28 22:49 [PATCH v2 0/4] Topstar ACPI LED Workaround Guillaume Douézan-Grard
2017-10-28 22:50 ` [PATCH v2 1/4] platform/x86: topstar-laptop: non-functional changes Guillaume Douézan-Grard
2017-11-03 12:40 ` Andy Shevchenko
2017-10-28 22:51 ` [PATCH v2 2/4] platform/x86: topstar-laptop: change to generic module Guillaume Douézan-Grard
2017-11-03 12:43 ` Andy Shevchenko
2017-10-28 22:52 ` [PATCH v2 3/4] platform/x86: topstar-laptop: add platform device Guillaume Douézan-Grard
2017-11-03 12:47 ` Andy Shevchenko
2017-10-28 22:53 ` [PATCH v2 4/4] platform/x86: topstar-laptop: add optional WLAN LED workaround Guillaume Douézan-Grard
2017-11-03 12:50 ` Andy Shevchenko
2017-11-03 15:07 ` Guillaume Douézan-Grard [this message]
2017-11-05 13:28 ` Andy Shevchenko
2017-11-05 22:34 ` Darren Hart
2017-11-08 0:25 ` Guillaume Douézan-Grard
2017-11-08 10:26 ` Andy Shevchenko
2017-11-03 11:56 ` [PATCH v2 0/4] Topstar ACPI LED Workaround Andy Shevchenko
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=20171103150735.GA13165@localhost \
--to=gdouezangrard@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--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