Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754235AbdIZHwt convert rfc822-to-8bit (ORCPT ); Tue, 26 Sep 2017 03:52:49 -0400 Received: from mga02.intel.com ([134.134.136.20]:11599 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751484AbdIZHwp (ORCPT ); Tue, 26 Sep 2017 03:52:45 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,440,1500966000"; d="scan'208";a="1175843441" From: "Zheng, Lv" To: "Wysocki, Rafael J" , "Rafael J . Wysocki" , "Brown, Len" CC: Lv Zheng , "linux-kernel@vger.kernel.org" , "linux-acpi@vger.kernel.org" Subject: RE: [PATCH v4 0/3] ACPI / EC: Fix EC event handling issues Thread-Topic: [PATCH v4 0/3] ACPI / EC: Fix EC event handling issues Thread-Index: AQHTIjCpRLOwzrPnI0GZZjQ8AlUQEqLG85XQ Date: Tue, 26 Sep 2017 07:52:14 +0000 Message-ID: <1AE640813FDE7649BE1B193DEA596E886CF6BFA7@SHSMSX101.ccr.corp.intel.com> References: <99f23db65bbe89ee856018629654584a96734c84.1501141963.git.lv.zheng@intel.com> In-Reply-To: Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYTM2NWY5OTctMGE2OC00OWJmLWE4ZDctNTUyMGVjNmM5ZGFmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6ImloK0hLVDVxdXRTY0xcL3FvZ0t4WGloZ1VJMkRIdnZROEx4bGMrNjJrMWhjPSJ9 x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1743 Lines: 46 Hi, Rafael I'm now working on v5 of this series. Which 1. splits root causes in a more detailed way, 2. clarifies root causes in patch description with real bugs, and 3. is safer according to the known EC FW behaviors. So you can discard v3/v4 from the patchwork site. And I'll post v5 when everything is cleared to me. Thanks and best regards Lv > From: Zheng, Lv > Subject: [PATCH v4 0/3] ACPI / EC: Fix EC event handling issues > > EC events are special, required to be handled during suspend/resume. But > there are special logics in Linux causing several issues related to the EC > event handling: > 1. During noirq stage, Linux cannot detect EC events which are target > driven. > 2. When EC event handling is enabled later than the other drivers, order > problem could be observed. > When fixing these problems, care should be taken to not to trigger > regressions to the following problem which has alredy been fixed using > different approach): > 3. When EC event handling is enabled before the end of the noirq stage, > EC event handling may stuck. > This patchset fixes these issues. > > v4 of this patch series re-orders the fixes so that the fix of the problem > 2 could be independent against the fix of the problem 1, this is done by > refining the fix of the problem 2, making it immune to the problem 3. > > Lv Zheng (3): > ACPI / EC: Fix possible driver order issue by moving EC event handling > earlier > ACPI / EC: Add event detection support for noirq stages > ACPI / EC: Enable noirq stage event detection > > drivers/acpi/ec.c | 116 +++++++++++++++++++++++++++++++++++++++++++++--- > drivers/acpi/internal.h | 1 + > 2 files changed, 111 insertions(+), 6 deletions(-) > > -- > 2.7.4