From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755249AbdLUTLF (ORCPT ); Thu, 21 Dec 2017 14:11:05 -0500 Received: from mail-it0-f68.google.com ([209.85.214.68]:36697 "EHLO mail-it0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754579AbdLUTLB (ORCPT ); Thu, 21 Dec 2017 14:11:01 -0500 X-Google-Smtp-Source: ACJfBosfdgmP/W/naD898M6xqUjIfk5Mn60jrmbRKO/Y8oEYKlEN/EkfmEoHEEhCn72Up3EwtP3TgA== Date: Thu, 21 Dec 2017 11:10:58 -0800 From: Brian Norris To: "Ghorai, Sukumar" Cc: Guenter Roeck , "gregkh@linuxfoundation.org" , "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" , "Bag, Amit K" , Oliver Neukum , Marcel Holtmann , 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 Message-ID: <20171221191057.GA222103@google.com> References: <20171218152852.624624481@linuxfoundation.org> <20171220195112.GA1287@google.com> <20171221083052.GA19501@kroah.com> <20171221182639.GA30333@roeck-us.net> <20171221185830.GA219523@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Dec 21, 2017 at 07:05:03PM +0000, Ghorai, Sukumar wrote: > >>On Thu, Dec 21, 2017 at 06:52:31PM +0000, Ghorai, Sukumar wrote: > >> Bug: platform can't wake using LE mouse/ keyboatd or any other LE I/O > >> device connected. > > > >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? Brian