<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [HSW/CHT/PNV/IVB] ACPI _LID usage model change" href="https://bugs.freedesktop.org/show_bug.cgi?id=100923#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [HSW/CHT/PNV/IVB] ACPI _LID usage model change" href="https://bugs.freedesktop.org/show_bug.cgi?id=100923">bug 100923</a> from <a class="email" href="mailto:lv.zheng@intel.com" title="Lv Zheng <lv.zheng@intel.com>"> Lv Zheng</a> <pre>As Peter mentioned, DMs (desktop managers) can start at any time. While there are tables (mostly from microsoft) that BIOS won't notify lid state change to OS (there are even worse case that lid state is always "closed"). Thus OS driver/input layer cached lid state value is not reliable for such notebooks. For current kernel input ABI, input driver can only use a timer to timely refresh the cached value to provide reliable lid state to userspace. But the timer is not power friendly. We should find different solutions. Either input layer could provide a new callback for driver. When userspace reads the latest lid state from kernel, input layer may invoke "get_state()" callback to update the cached state. Or userspace GMs should stop using lid state to determine window layout and monitor status. That's reasonable as ACPI lid is not provided for this purpose. Thanks Lv</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>