linux-kernel - [patch] Reporting the lid status using INPUT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 27 Jun 2007 20:42:25 +0100
From:	Richard Hughes <hughsient@...il.com>
To:	len.brown@...el.com
Cc:	Dmitry Torokhov <dtor@...ightbb.com>,
	linux-acpi <linux-acpi@...r.kernel.org>,
	Bastien Nocera <hadess@...ess.net>,
	David Zeuthen <david@...ar.dk>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: [patch] Reporting the lid status using INPUT

Len,

* user shuts lid, initiates suspend
{lid is reported down}
* user opens lid, resume completes

But the lid INPUT up event is not sent. This works if you don't initiate
suspend when you shut the lid (blank screen for instance) -- so I know
my hardware is okay.

I see:
input_report_switch(input, SW_LID, !state);

in response to an event, but in a resume hook we should probably do
acpi_evaluate_integer(handle, "_LID", NULL, &state) and then send an
event, just so userspace is aware of what the state of the panel is.

If switch state matches to what input layer thinks it is the event will
not be sent.

Signed-off-by: Richard Hughes <richard@...hsie.com>

Download attachment "button-resume.patch" of type "message/rfc822" (2210 bytes)