public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Rafi Rubin <rafi@seas.upenn.edu>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] dell-wmi Switch support and Tablet switch definition
Date: Fri, 19 Jun 2009 15:28:48 -0400	[thread overview]
Message-ID: <4A3BE6F0.7090107@seas.upenn.edu> (raw)
In-Reply-To: <20090619140228.GA21354@srcf.ucam.org>

Matthew Garrett wrote:
> On Fri, Jun 19, 2009 at 07:15:12AM -0400, Rafi Rubin wrote:
>> Added a bit of missing code needed to handle switch events.
>>
>> Added the definitions for the hinge rotation as seen on the
>> Latitude XT tablet.
> 
> Having thought about this a bit more, I think there's a pretty 
> fundamental problem right now - we don't know whether we're in tablet 
> mode or not when we boot, so can't set the initial state. Software that 
> depends on that may be rather confused as a result...

I agree polling the tablet state would be a good thing.  But that does not mean we should not
support the signals until we are ready to support polling.

If you are suggesting that we should not use an EV_SW because we will eventually poll the hardware
instead of keeping the state in software, then I have no problem with sending keys or other events.

However if you still think keeping the state in software and using EV_SW is a good idea, this code
is independent of the probe code.  And I think the value of having this support is well worth the
potential harm.  After all, it thinks its in non-tablet mode until the signal comes in that its
switching to tablet.  How is this any worse than always thinking its in non-tablet mode?

Rafi

  reply	other threads:[~2009-06-19 19:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19 11:15 [PATCH] dell-wmi Switch support and Tablet switch definition Rafi Rubin
2009-06-19 14:02 ` Matthew Garrett
2009-06-19 19:28   ` Rafi Rubin [this message]
2009-06-19 19:40     ` Matthew Garrett
2009-06-19 20:31       ` Rafi Rubin
2009-06-19 20:34         ` 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=4A3BE6F0.7090107@seas.upenn.edu \
    --to=rafi@seas.upenn.edu \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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