From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1757161AbdLWQO3 (ORCPT <rfc822;w@1wt.eu>);
        Sat, 23 Dec 2017 11:14:29 -0500
Received: from mail.linuxfoundation.org ([140.211.169.12]:48064 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752279AbdLWQO1 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Sat, 23 Dec 2017 11:14:27 -0500
Date: Sat, 23 Dec 2017 17:14:28 +0100
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Ghorai, Sukumar" <sukumar.ghorai@intel.com>
Cc: Brian Norris <briannorris@chromium.org>,
        Guenter Roeck <linux@roeck-us.net>,
        Matthias Kaehlcke <mka@chromium.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "stable@vger.kernel.org" <stable@vger.kernel.org>,
        "Bag, Amit K" <amit.k.bag@intel.com>, Oliver Neukum <oneukum@suse.com>,
        Marcel Holtmann <marcel@holtmann.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
Message-ID: <20171223161428.GB21326@kroah.com>
References: <D73ECEF0C711E34A8F972E4B87F54005799013B0@ORSMSX114.amr.corp.intel.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>
 <D73ECEF0C711E34A8F972E4B87F54005799023AC@ORSMSX114.amr.corp.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <D73ECEF0C711E34A8F972E4B87F54005799023AC@ORSMSX114.amr.corp.intel.com>
User-Agent: Mutt/1.9.2 (2017-12-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Sat, Dec 23, 2017 at 03:53:57PM +0000, Ghorai, Sukumar wrote:
> >> > 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?

4.12 is long end-of-life, I don't know what you expect to happen there.

4.14 is already released, this needs to be done for 4.15 first, right?

thanks,

greg k-h