Re: [WIP PATCH 0/4] Rework the unreliable LID switch exported by ACPI

From: Lennart Poettering <mzxreary@0pointer.de>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Len Brown <len.brown@intel.com>,
	systemd-devel@lists.freedesktop.org, linux-acpi@vger.kernel.org,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org, Lv Zheng <zetalog@gmail.com>,
	Lv Zheng <lv.zheng@intel.com>,
	linux-input@vger.kernel.org
Subject: Re: [WIP PATCH 0/4] Rework the unreliable LID switch exported by ACPI
Date: Wed, 7 Jun 2017 09:48:48 +0200	[thread overview]
Message-ID: <20170607074848.GE27006@gardel-login> (raw)
In-Reply-To: <20170601184632.2980-1-benjamin.tissoires@redhat.com>

On Thu, 01.06.17 20:46, Benjamin Tissoires (benjamin.tissoires@redhat.com) wrote:

> Hi,
> 
> Sending this as a WIP as it still need a few changes, but it mostly works as
> expected (still not fully compliant yet).
> 
> So this is based on Lennart's comment in [1]: if the LID state is not reliable,
> the kernel should not export the LID switch device as long as we are not sure
> about its state.

Ah nice! I (obviously) like this approach.

> Note that systemd currently doesn't sync the state when the input node just
> appears. This is a systemd bug, and it should not be handled by the kernel
> community.

Uh if this is borked, we should indeed fix this in systemd. Is there
already a systemd github bug about this? If not, please create one,
and we'll look into it!

Thanks for working on this,

Lennart

-- 
Lennart Poettering, Red Hat
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel