From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Oliver Neukum <oneukum@suse.de>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] ACPI: Blacklist Win8 OSI for some HP laptop 2013 models
Date: Tue, 14 Jan 2014 16:44:57 +0000 [thread overview]
Message-ID: <20140114164457.GA8166@srcf.ucam.org> (raw)
In-Reply-To: <s5hsisqtsxf.wl%tiwai@suse.de>
On Tue, Jan 14, 2014 at 05:43:56PM +0100, Takashi Iwai wrote:
> At Tue, 14 Jan 2014 16:36:00 +0000,
> Matthew Garrett wrote:
> >
> > On Tue, Jan 14, 2014 at 05:33:50PM +0100, Takashi Iwai wrote:
> >
> > > For the rfkill part, it depends on the user-space. Without the patch,
> > > it sends a scan code, and OS is supposed to do rfkill via each
> > > driver. The proper key mapping would be needed. Not sure about the
> > > LED state on the WiFi button, though, whether it's properly controlled
> > > by WiFi and/or BT driver. With the patch, all rfkill and LED are
> > > handled by BIOS, so it works as is.
> >
> > Ok, so userspace needs to work - there's plenty of hardware that only
> > sends a scancode already. Let's just add the keycode and then remove
> > this once the backlight stuff is fixed.
>
> Yes, sounds feasible.
Oh, and once we've got the keycode in it's possible to handle this
in-kernel - you just need rfkill-input.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2014-01-14 16:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 11:14 [PATCH RESEND] ACPI: Blacklist Win8 OSI for some HP laptop 2013 models Takashi Iwai
2014-01-13 11:46 ` Rafael J. Wysocki
2014-01-13 11:33 ` Takashi Iwai
2014-01-14 16:12 ` Matthew Garrett
2014-01-14 16:33 ` Takashi Iwai
2014-01-14 16:36 ` Matthew Garrett
2014-01-14 16:43 ` Takashi Iwai
2014-01-14 16:44 ` Matthew Garrett [this message]
2014-01-14 16:42 ` Rafael J. Wysocki
2014-01-14 16:34 ` Matthew Garrett
2014-01-14 16:53 ` Rafael J. Wysocki
2014-01-14 16:42 ` Matthew Garrett
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=20140114164457.GA8166@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oneukum@suse.de \
--cc=rjw@rjwysocki.net \
--cc=tiwai@suse.de \
/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).