From: "Ghorai, Sukumar" <sukumar.ghorai@intel.com>
To: Brian Norris <briannorris@chromium.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
        Marcel Holtmann <marcel@holtmann.org>,
        "Oliver Neukum" <oneukum@suse.com>, Guenter Roeck <linux@roeck-us.net>,
        "stable@vger.kernel.org" <stable@vger.kernel.org>
CC: "Bag, Amit K" <amit.k.bag@intel.com>,
        Matthias Kaehlcke <mka@chromium.org>, Todd Broch <tbroch@chromium.org>,
        Rajat Jain <rajatja@chromium.org>, Miao Chou <mcchou@chromium.org>,
        "Rao Pv, Sadashiva" <sadashiva.rao.pv@intel.com>
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//ezfw
Date: Thu, 21 Dec 2017 19:23:27 +0000
Message-ID: <D73ECEF0C711E34A8F972E4B87F54005799013E5@ORSMSX114.amr.corp.intel.com>
References: <20171218152852.624624481@linuxfoundation.org>
 <20171220195112.GA1287@google.com> <20171221083052.GA19501@kroah.com>
 <CA+ASDXNABgtZCj7SF=-LvBZGwWB0uo4BiWGTzpmhEZcQUkZPRA@mail.gmail.com>
 <20171221182639.GA30333@roeck-us.net>
 <D73ECEF0C711E34A8F972E4B87F5400579901388@ORSMSX114.amr.corp.intel.com>
 <20171221185830.GA219523@google.com>
 <D73ECEF0C711E34A8F972E4B87F54005799013B0@ORSMSX114.amr.corp.intel.com>
 <20171221191057.GA222103@google.com>
In-Reply-To: <20171221191057.GA222103@google.com>
Accept-Language: en-US
Content-Language: en-US
dlp-product: dlpe-windows
dlp-version: 11.0.0.116
dlp-reaction: no-action
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8BIT
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1015
Lines: 21

>> >Could you ever? If not, that looks like a feature request to me...
>> Agree, feature request... however  we need this feature for rapid use of
>Bluetooth LE devices.
>
>Is that what -stable is for now? For getting your pet feature enabled more
>quickly? I thought that's what Linaro was for, or something like that.
>
>Besides the poor reasoning of the above (IMO): isn't that something you can also
>configure in user space? So, upgrade user space (e.g., BlueZ) to resolve the
>regressions that have been reported, then write the appropriate udev rules to
>turn this on? Or is that too "slow" for you?
Free to take decision..

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.
2. Even the behavior is same in existing stable code, when connect the
Bluetooth BR/EDR mouse (io device), as It will enable the usb-wakeup feature/flag,

>
>Brian