Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752226AbdFOC4c (ORCPT ); Wed, 14 Jun 2017 22:56:32 -0400 Received: from mga14.intel.com ([192.55.52.115]:61733 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752121AbdFOC43 (ORCPT ); Wed, 14 Jun 2017 22:56:29 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,342,1493708400"; d="scan'208";a="98133842" From: "Zheng, Lv" To: Benjamin Tissoires , Lennart Poettering CC: "Wysocki, Rafael J" , "Rafael J . Wysocki" , "Brown, Len" , Lv Zheng , Peter Hutterer , "linux-acpi@vger.kernel.org" , "systemd-devel@lists.freedesktop.org" , "linux-kernel@vger.kernel.org" , "linux-input@vger.kernel.org" Subject: RE: [systemd-devel] [WIP PATCH 0/4] Rework the unreliable LID switch exported by ACPI Thread-Topic: [systemd-devel] [WIP PATCH 0/4] Rework the unreliable LID switch exported by ACPI Thread-Index: AQHS2wd01O/IlIfVsk2vy8j9OHBM16IYiNMAgAmUZoCAAzAyYA== Date: Thu, 15 Jun 2017 02:52:57 +0000 Message-ID: <1AE640813FDE7649BE1B193DEA596E886CED0386@SHSMSX101.ccr.corp.intel.com> References: <20170601184632.2980-1-benjamin.tissoires@redhat.com> <20170607074848.GE27006@gardel-login> <20170613100617.GD29589@mail.corp.redhat.com> In-Reply-To: <20170613100617.GD29589@mail.corp.redhat.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNTQ2OTU1ODUtZDlmMC00ZTdiLTgxOWYtZTNiN2NjZDkzMWE1IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6IlNGeW5BY1pvYWMwRUxDMWExYnBIK0xUVHN1STVuMk1DYlA5T1J5UE5TOU09In0= x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id v5F2v8cb005674 Content-Length: 2100 Lines: 55 Hi, Benjamin > From: Benjamin Tissoires [mailto:benjamin.tissoires@redhat.com] > Subject: Re: [systemd-devel] [WIP PATCH 0/4] Rework the unreliable LID switch exported by ACPI > > Hi, > > [Sorry for the delay, I have been sidetracked from this] > > On Jun 07 2017 or thereabouts, Lennart Poettering wrote: > > 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. > > Heh. Now I just need to convince Lv that it's the right approach. I feel we don't have big conflicts. And I already took part of your idea into this patchset: https://patchwork.kernel.org/patch/9771121/ https://patchwork.kernel.org/patch/9771119/ I tested my surface pros with Ubuntu, they are working as expected. > > > 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! > > I don't think there is. I haven't raised it yet because I am not so sure > this will not break again those worthless unreliable LID, and if we play > whack a mole between the kernel and user space, things are going to be > nasty. So I'd rather have this fixed in systemd along with the > unreliable LID switch knowledge, so we are sure that the kernel behaves > the way we expect it to be. This is my feeling: We needn't go that far. We can interpret "input node appears" into "default input node state". That's what you want for acpi button driver - we now defaults to "method" mode. What's your opinion? Thanks Lv