public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Len Brown <lenb@kernel.org>
Cc: Daniel Drake <dsd@gentoo.org>,
	linux-acpi@vger.kernel.org, luming.yu@intel.com
Subject: Re: Laptop screen doesn't come on when lid is reopened
Date: Wed, 9 May 2007 19:00:07 -0300	[thread overview]
Message-ID: <20070509220007.GC9055@khazad-dum.debian.net> (raw)
In-Reply-To: <200705091148.21097.lenb@kernel.org>

On Wed, 09 May 2007, Len Brown wrote:
> Assuming that it works on the Dells, hopefully more
> than the Dells, and doesn't break any others...
...
> Then the button driver should take the lid event and
> cause the code in the video driver to be invoked.
> I'm not sure what the best method for inter-driver
> event like this, since both of them can be modules.

It will break all laptops which don't do anything special on lid events
other than report it to the OS, so that we can do whatever we want
(typically tell HAL or some script to suspend if the lid is closed).  Like,
say, thinkpads.

> Finally, the video driver should have suspend/resume methods
> that poke _DSS and that should fix the Dell video on S3.

Yes, that seems like a good idea.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2007-05-09 22:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-06 20:17 Laptop screen doesn't come on when lid is reopened Daniel Drake
2007-05-09 15:48 ` Len Brown
2007-05-09 22:00   ` Henrique de Moraes Holschuh [this message]
2007-05-09 22:04     ` Matthew Garrett
2007-05-09 22:30       ` Henrique de Moraes Holschuh
2007-06-01  3:03   ` Daniel Drake

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=20070509220007.GC9055@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=dsd@gentoo.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=luming.yu@intel.com \
    /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