linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Richard Hughes <hughsient@gmail.com>
Cc: trenn@suse.de, Len Brown <lenb@kernel.org>,
	Dmitry Torokhov <dtor@insightbb.com>,
	linux-acpi <linux-acpi@vger.kernel.org>,
	linux-input <linux-input@atrey.karlin.mff.cuni.cz>,
	Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [patch] Refresh lid state on resume
Date: Tue, 31 Jul 2007 11:08:42 +0200	[thread overview]
Message-ID: <200707311108.42947.rjw@sisk.pl> (raw)
In-Reply-To: <1185809610.24649.3.camel@hughsie-laptop>

On Monday, 30 July 2007 17:33, Richard Hughes wrote:
> On Mon, 2007-07-30 at 17:21 +0200, Thomas Renninger wrote:
> > On Tue, 2007-07-17 at 12:15 +0100, Richard Hughes wrote:
> > > On resume we need to refresh the lid status as we will not get an event if
> > > the lid opening was what triggered the suspend.
> > > This manifests itself in users never getting a "lid open" event when a
> > > suspend happens because of lid close on hardware that supports wake on
> > > lid open. This makes userspace gets very confused indeed.
> > > Patch inline (and also attached) forces a check of the lid status in the
> > > resume handler.
> > Is this a general problem on all machines?
> 
> I've only seen myself it on new ThinkPads such as the T61 and X60,
> although I've been getting a few bug reports about other IBM laptops.
> 
> > Or does this only happen if "shutdown" suspend mode is used?
> 
> No, I don't believe so.
> 
> > I could imagine a lot machines let it up to OS to check for LID state
> > change, then this one should be added.
> 
> I guess it's up to the BIOS, and I don't think this refresh hurts any
> machines that implement a notify on resume, and fixes a fair few
> machines that don't.

AFAICS, the notify doesn't seem to work very well on some machines.

Are there any downsides of the $subject patch?

Greetings,
Rafael


-- 
"Premature optimization is the root of all evil." - Donald Knuth

  reply	other threads:[~2007-07-31  9:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 11:15 [patch] Refresh lid state on resume Richard Hughes
2007-07-30 15:21 ` Thomas Renninger
2007-07-30 15:33   ` Richard Hughes
2007-07-31  9:08     ` Rafael J. Wysocki [this message]
2007-07-31  9:07       ` Richard Hughes
2007-07-31 10:42         ` Thomas Renninger
2007-07-31 13:18           ` Richard Hughes
2007-07-31 13:42           ` Rafael J. Wysocki
2007-07-31 14:26             ` [PATCH] Enable GPEs before _WAK is called Thomas Renninger
2007-07-31 15:09               ` Rafael J. Wysocki
2007-07-31 12:53       ` [patch] Refresh lid state on resume Henrique de Moraes Holschuh

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=200707311108.42947.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=dtor@insightbb.com \
    --cc=hughsient@gmail.com \
    --cc=kay.sievers@vrfy.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=trenn@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).