From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Dmitry Gubenko <gubenko.dmitry@googlemail.com>,
Rezwanul Kabir <Rezwanul_Kabir@dell.com>,
Platform Driver x86 <platform-driver-x86@vger.kernel.org>
Subject: Re: dell-wmi - question concerning battery charge key functionality
Date: Wed, 24 Nov 2010 16:41:18 +0000 [thread overview]
Message-ID: <20101124164118.GA1811@srcf.ucam.org> (raw)
In-Reply-To: <20101112195322.GB1299@core.coreip.homeip.net>
On Fri, Nov 12, 2010 at 11:53:22AM -0800, Dmitry Torokhov wrote:
> > I'm using dell_wmi on my laptop (Dell Latitude e4300) which has
> > keybinds for toggling battery charging if AC adapter is available
> > (Fn+F2 and Fn+F3).
> > As far as i understand this functionality is not available as of now.
> > I get
> > dell-wmi: Received unknown WMI event (0x11)
>
> Looking at the code we are only prepared to handle 0x10 events. Rezwanul
> Kabir added the code to handle newer Dells so he might have an idea what
> event 0x11 is (CCed).
Fn+F2 should toggle the battery charging on and off. I believe that this
works fine and even updates the battery driver appropriately - we
probably just need to update dell-wmi not to emit a warning in that
case.
> > when pressing Fn+F2 and no reaction when pressing Fn+F3.
> >
Fn+F3 should end up sending KEY_BATTERY, and your userspace should use
that to display battery information.
So other than the warning generated by dell-wmi, I think this all works
as expected?
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2010-11-24 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4CDD1603.808@googlemail.com>
2010-11-12 19:53 ` dell-wmi - question concerning battery charge key functionality Dmitry Torokhov
2010-11-24 16:41 ` Matthew Garrett [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=20101124164118.GA1811@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=Rezwanul_Kabir@dell.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gubenko.dmitry@googlemail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.