From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: yakui_zhao <yakui.zhao@intel.com>
Cc: Fu Michael <michael_fu@linux.intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"Zhang, Rui" <rui.zhang@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"lenb@kernel.org" <lenb@kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [Intel-gfx] [RFC] i915/acpi: add lid status notification and detection
Date: Wed, 17 Jun 2009 16:10:39 -0700 [thread overview]
Message-ID: <20090617161039.45027d45@jbarnes-g45> (raw)
In-Reply-To: <1245205951.3583.169.camel@localhost.localdomain>
On Wed, 17 Jun 2009 10:32:31 +0800
yakui_zhao <yakui.zhao@intel.com> wrote:
> On Wed, 2009-06-17 at 02:33 +0800, Jesse Barnes wrote:
> > Well, what should we use then? Think of a common use case: you plug
> > in
> > an external monitor and shut your lid. Do we want to make the user
> > manually change their configuration? Or detect that the lid is no
> > longer in use? And what about the case where they boot with the lid
> > closed (e.g. in a docked scenario)? We want to support that
> > automatically too...
> This feature should work on most laptops. When the LID is closed, the
> LVDS is marked as disconnected.
>
> But this can't work for some boxes on which the initial Lid state is
> incorrect. We see such an exception on several laptops in ACPI
> bugzilla.
>
> If we expect this feature for most laptops, how about adding the
> exception boxes into the blacklist that doesn't support this feature?
Yeah, that's fine with me. Is there a list somewhere? Please don't
make me troll through ACPI bugzilla! :)
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-06-17 23:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 18:57 [RFC] i915/acpi: add lid status notification and detection Jesse Barnes
2009-05-14 1:22 ` yakui_zhao
2009-05-15 18:16 ` [PATCH] " Jesse Barnes
2009-05-19 17:15 ` [RFC] " Matthew Garrett
2009-05-21 8:57 ` Zhang Rui
2009-05-21 16:34 ` Jesse Barnes
2009-05-22 1:22 ` [Intel-gfx] " Fu Michael
2009-05-22 1:26 ` Matthew Garrett
2009-05-22 2:03 ` Zhang Rui
2009-05-27 8:58 ` Jesse Barnes
2009-05-27 13:41 ` Fu Michael
2009-06-11 7:16 ` yakui_zhao
2009-06-16 18:33 ` Jesse Barnes
2009-06-16 19:08 ` Corentin Chary
2009-06-17 2:32 ` yakui_zhao
2009-06-17 23:10 ` Jesse Barnes [this message]
2009-07-07 22:51 ` Jesse Barnes
2009-06-18 15:49 ` Thomas Renninger
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=20090617161039.45027d45@jbarnes-g45 \
--to=jbarnes@virtuousgeek.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=michael_fu@linux.intel.com \
--cc=mjg59@srcf.ucam.org \
--cc=rui.zhang@intel.com \
--cc=yakui.zhao@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