Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753091AbdLWPyC convert rfc822-to-8bit (ORCPT ); Sat, 23 Dec 2017 10:54:02 -0500 Received: from mga07.intel.com ([134.134.136.100]:14302 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751279AbdLWPyA (ORCPT ); Sat, 23 Dec 2017 10:54:00 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,446,1508828400"; d="scan'208";a="14129464" From: "Ghorai, Sukumar" To: "gregkh@linuxfoundation.org" , Brian Norris CC: Guenter Roeck , Matthias Kaehlcke , "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" , "Bag, Amit K" , Oliver Neukum , Marcel Holtmann , Todd Broch , Rajat Jain , Miao Chou , "Rao Pv, Sadashiva" Subject: RE: [PATCH 4.4 009/115] Bluetooth: btusb: driver to enable the usb-wakeup feature Thread-Topic: [PATCH 4.4 009/115] Bluetooth: btusb: driver to enable the usb-wakeup feature Thread-Index: AQHTeBiC8oVj3QTsi0Oqz0MyEHEZXaNNLbWAgADUPACAAJQTgIAAEmKA//9/TxCAAImaAP//elNQgAABBRCAAIghAIAADxWAgAALjgCAAAFNgIAADZ2AgACqGACAAKSoAIABBtsA///lqEA= Date: Sat, 23 Dec 2017 15:53:57 +0000 Message-ID: References: <20171221185830.GA219523@google.com> <20171221191057.GA222103@google.com> <20171221200457.GB24020@roeck-us.net> <20171221204618.GB29509@kroah.com> <20171221205057.GC29509@kroah.com> <20171221213941.GD24020@roeck-us.net> <20171222074828.GA15565@kroah.com> <20171222173747.GB127515@google.com> <20171223091836.GF13832@kroah.com> In-Reply-To: <20171223091836.GF13832@kroah.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYmYzMDU4NjItMzY3NS00YWU0LWI4NjItZTY1NjdhOGJkMmNjIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiIrZ2daTTdrRTV0VTdxOEgyNmU4Z05MS2YrXC9vZktnb3QyRkdXSzNBRHg2bDNIdFBmdmtvUjdUQ00zVFk1WmN3VCJ9 x-ctpclassification: CTP_IC x-originating-ip: [10.22.254.139] 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: 1045 Lines: 19 >> > included in 4.14-rc1, so something needs to be done in Linus's tree >> > to resolve this issue, otherwise people will hit this as a >> > regression when moving to 4.14 or newer. >> >> Well, I wouldn't object to reverting it in Linus' tree too, since >> AFAIK, this is something that can be configured by user-space policy, >> no? And that way, no user space is surprised by the sudden additional >> requirements on managing bluetooth wakeup. Wakeup from Bluetooth will be observed as long as USB wakeup is configured from user space or kernel space or connected to any Bluetooth HID devices. And we don't want to support the wakeup from BT HID devide. The solution looks like disable Bluetooth in S3 entry? Looks we are trying to hide the other problems in a system, and reverting this patch. > >I agree, please work with the bluetooth developers to make this happen. >They seem to be ignoring patches right now, so you might have to kick them a few >times :( Do you suggest submitter to send the revert request to 4.12 and 4.14 kernel?