From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755364AbdLUUP2 convert rfc822-to-8bit (ORCPT ); Thu, 21 Dec 2017 15:15:28 -0500 Received: from mga06.intel.com ([134.134.136.31]:52348 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753742AbdLUUP0 (ORCPT ); Thu, 21 Dec 2017 15:15:26 -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,437,1508828400"; d="scan'208";a="13713463" From: "Ghorai, Sukumar" To: Guenter Roeck CC: Brian Norris , "linux-kernel@vger.kernel.org" , "gregkh@linuxfoundation.org" , Marcel Holtmann , "Oliver Neukum" , "stable@vger.kernel.org" , "Bag, Amit K" , Matthias Kaehlcke , 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//elNQgAABBRCAAIghAP//ezfwABKv3AAAELv+kA== Date: Thu, 21 Dec 2017 20:15:23 +0000 Message-ID: References: <20171218152852.624624481@linuxfoundation.org> <20171220195112.GA1287@google.com> <20171221083052.GA19501@kroah.com> <20171221182639.GA30333@roeck-us.net> <20171221185830.GA219523@google.com> <20171221191057.GA222103@google.com> <20171221201046.GC24020@roeck-us.net> In-Reply-To: <20171221201046.GC24020@roeck-us.net> 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: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiODYxODIyMzgtMWYzNy00NWIwLTk0NzgtZmFkYTAzOGI0M2M1IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiJ6M1FoTERWN2ZFUHFybEhtNGF0V2x0Z1hKd0tMektwUHhSUnVEVUZ4RWJjbE14VkJDKzk5SlhNeGE3VXVlWGNmIn0= x-ctpclassification: CTP_IC x-originating-ip: [10.22.254.138] 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 >> I understand this feature is creating instability in other area. >> However - 1. the problem will remain same when enable the usb-wakeup >> feature form kernel or user-space or udev rule, and as long LE device is >connected. > >There is a slight difference of leaving the decision to the user (or to >userspace) or forcing it down the throat of everyone by adding it to the kernel. > >Your statement "I understand this feature is creating instability in other area" >should really be a wakeup call. It almost sounds like you are aware that it is >causing problems, but you don't care because it fits _your_ needs. I hope that is >not the case, but if it is, please keep in mind that you are not the only user of the >Linux kernel. No I don't know what is the problem here... As mentioned, keeping wake up enable(default) is same as BR/EDR mouse connected. Hence you will see the same platform behavior when BR/EDR mouse connected, and Without this patch. > >Thanks, >Guenter