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 16:31:59 -0400	[thread overview]
Message-ID: <4A3BF5BF.5030102@seas.upenn.edu> (raw)
In-Reply-To: <20090619194009.GA28382@srcf.ucam.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Matthew Garrett wrote:
> On Fri, Jun 19, 2009 at 03:28:48PM -0400, Rafi Rubin wrote:
> 
>> 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.
> 
> No, my point is that there's little benefit in providing EV_SW if the 
> initial value is going to be wrong. Software simply can't depend on it. 
> The code's absolutely fine, but there's a risk that it'll break 
> otherwise working desktops until we know how to set the initial value.


The signal is not a toggle.  Its an explicit "going to tablet" and "coming from tablet".  And the
initial value is "non-tablet" mode, which is what must be assumed without this support.

So the only new case where a wrong assumption may be made is if the screen is flipped out of tablet
mode during suspend or hibernate.  But we _don't_ have the potential of a toggle being inverted and
it rotating the screen to something silly every time you flip it.

I think the benefits of the partial support far outweight the potential hazards.


That being said, if you have any clue how to probe the state, I would be very happy to help you.
And I'd agree that signals can wait.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAko79b8ACgkQwuRiAT9o60+VowCg5zvB16xzUz6w7cqP6twu4xKv
9o0AoJuG3v9qkiB8SXVpk/D9nud2A8FM
=h/y8
-----END PGP SIGNATURE-----

  reply	other threads:[~2009-06-19 20:32 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
2009-06-19 19:40     ` Matthew Garrett
2009-06-19 20:31       ` Rafi Rubin [this message]
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=4A3BF5BF.5030102@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