From: Seth Forshee <seth.forshee@canonical.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dell-wmi: Change debug statements from pr_info to pr_debug
Date: Wed, 7 Dec 2011 10:43:15 -0600 [thread overview]
Message-ID: <20111207164315.GE15875@thinkpad-t410> (raw)
In-Reply-To: <20111121223209.GA16955@srcf.ucam.org>
On Mon, Nov 21, 2011 at 10:32:09PM +0000, Matthew Garrett wrote:
> > > On Mon, Nov 21, 2011 at 03:14:38PM -0600, Seth Forshee wrote:
> > > > On Mon, Nov 21, 2011 at 08:52:30PM +0000, Matthew Garrett wrote:
> > > > > They're intended to be there, in the same way that the keyboard code
> > > > > generates unknown scancode errors. We want to know when users have keys
> > > > > that don't work.
> > > >
> > > > All right, but what about the unknown WMI events? Those are the bigger
> > > > problem anyway, as at least one machine (the Latitude XT2) can generate
> > > > a lot of these messages for unknown reasons. It doesn't appear that
> > > > anyone has been making use of these messages since we still only support
> > > > one event. Would you object to demoting that one?
> > >
> > > Those can probably be ignored, but again it would be nice to find out
> > > what they actually mean so we know whether we can do anything with them.
> > > Any chance of you being able to work with Dell on that?
> >
> > I'll see what I can do.
>
> Great, thanks. If we don't work out what they are then we can certainly
> drop the error - I agree that telling the user about something that just
> confuses us isn't helpful.
I've tried a few different avenues trying to get this informatin out of
Dell, but so far I've gotten very little. 0x11 is a status change event
notification, apparently sent when there are changes to things like
battery charge status, ALS level, etc. I haven't received any
information about how to interpret the payload, and what little Dell kit
I have doesn't seem to send this event.
I've received no informtion at all on the 0xf event. The only thing I
really know about is from a user report stating that it's seen on the
XT2 when opening and closing the lid in notebook orientation.
I can take further action if Dell becomes more forthcoming, but I'm not
holding out much hope at this point. So I can send a new patch demoting
only the WMI event message to debug, or I can silence it only for these
specific events. Do you have a preference?
Thanks,
Seth
next prev parent reply other threads:[~2011-12-07 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 20:48 [PATCH] dell-wmi: Change debug statements from pr_info to pr_debug Seth Forshee
2011-11-21 20:52 ` Matthew Garrett
2011-11-21 21:10 ` Corentin Chary
2011-11-21 21:14 ` Seth Forshee
2011-11-21 21:18 ` Matthew Garrett
2011-11-21 22:29 ` Seth Forshee
2011-11-21 22:32 ` Matthew Garrett
2011-12-07 16:43 ` Seth Forshee [this message]
2011-12-07 20:22 ` Rezwanul_Kabir
2011-12-07 21:15 ` Seth Forshee
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=20111207164315.GE15875@thinkpad-t410 \
--to=seth.forshee@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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