[Bug 100923] ACPI _LID usage model change

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon May 15 09:29:52 UTC 2017


https://bugs.freedesktop.org/show_bug.cgi?id=100923

Benjamin Tissoires <benjamin.tissoires at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Product|Wayland                     |DRI
          Component|libinput                    |DRM/Intel
         QA Contact|                            |intel-gfx-bugs at lists.freede
                   |                            |sktop.org
           Assignee|wayland-bugs at lists.freedesk |intel-gfx-bugs at lists.freede
                   |top.org                     |sktop.org

--- Comment #5 from Benjamin Tissoires <benjamin.tissoires at gmail.com> ---
Well, this issue is not related to libinput but to the use of acpi_lid_open()
by the intel i915 driver (in drivers/gpu/drm/i915/intel_lvds.c).

It has been shown that on some platforms the ACPI _LID call is not reliable and
only the closed event is sent.

drivers/gpu/drm/i915/intel_lvds.c ignores the value provided by the lid
notifier (unsigned long val parameter), and does it's own call to
acpi_lid_open().

IMO, we should either enforce i915 to use the provided value (as sent by Lv in
https://patchwork.kernel.org/patch/9713021/), or make sure acpi_lid_open()
returns the fixed value (so no change from the i915 driver would be required).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170515/581680b4/attachment.html>


More information about the intel-gfx-bugs mailing list