From: Oliver Neukum <oneukum@suse.com>
To: Marcel Holtmann <marcel@holtmann.org>,
Sukumar Ghorai <sukumar.ghorai@intel.com>,
Greg Kroah-Hartman <greg@kroah.com>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
Amit K Bag <amit.k.bag@intel.com>,
"Gustavo F. Padovan" <gustavo@padovan.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btusb: driver to enable the usb-wakeup feature
Date: Wed, 16 Aug 2017 11:42:43 +0200 [thread overview]
Message-ID: <1502876563.6606.16.camel@suse.com> (raw)
In-Reply-To: <D92CCD61-177E-41F1-A644-FBDF42095F0E@holtmann.org>
Am Mittwoch, den 16.08.2017, 11:37 +0200 schrieb Marcel Holtmann:
> Hi Oliver,
>
> >
> > BT-Controller connected as platform non-root-hub device and
> > usb-driver initialize such device with wakeup disabled,
> > Ref. usb_new_device().
> >
> > At present wakeup-capability get enabled by hid-input device from usb
> > function driver(e.g. BT HID device) at runtime. Again some functional
> > driver does not set usb-wakeup capability(e.g LE HID device implement
> > as HID-over-GATT), and can't wakeup the host on USB.
> >
> > Most of the device operation (such as mass storage) initiated from host
> > (except HID) and USB wakeup aligned with host resume procedure. For BT
> > device, usb-wakeup capability need to enable form btusc driver as a
> > generic solution for multiple profile use case and required for USB remote
> > wakeup (in-bus wakeup) while host is suspended. Also usb-wakeup feature
> > need to enable/disable with HCI interface up and down.
> >
> > Signed-off-by: Sukumar Ghorai <sukumar.ghorai@intel.com>
> > Signed-off-by: Amit K Bag <amit.k.bag@intel.com>
Acked-by: Oliver Neukum <oneukum@suse.com>
next prev parent reply other threads:[~2017-08-16 9:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 21:46 [PATCH] Bluetooth: btusb: driver to enable the usb-wakeup feature Sukumar Ghorai
2017-08-16 9:37 ` Marcel Holtmann
2017-08-16 9:42 ` Oliver Neukum [this message]
2017-08-16 9:49 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1502876563.6606.16.camel@suse.com \
--to=oneukum@suse.com \
--cc=amit.k.bag@intel.com \
--cc=greg@kroah.com \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=sukumar.ghorai@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox