All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Poulain <loic.poulain@intel.com>
To: "Ge, Ethan" <ethan.ge@intel.com>, "An, Tedd" <tedd.an@intel.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCHv2] Bluetooth: btusb: Fix Intel controller hang after shutdown
Date: Mon, 08 Jun 2015 10:45:11 +0200	[thread overview]
Message-ID: <55755617.8080302@intel.com> (raw)
In-Reply-To: <86D221DC0B85F94D9B05B97827669A3403CA6EA0@PGSMSX106.gar.corp.intel.com>

Hi Ethan,

> I am helping Tedd to test this patch now, but I have a question about this patch.
>
> For your comment It looks like you want to send HCI RESET command to controller first when BT enabled, then I found below patch also do same thing as your patch. May I know any difference for your patch? Thanks.

> commit dffd30ee9619ccd7153f1861ba0436bbc4400f36
> Author: Tedd Ho-Jeong An <tedd.an@intel.com>
> Date:   Fri Apr 19 09:57:43 2013 -0700
>
>      Bluetooth: Add support for Intel Bluetooth device [8087:07dc]

setup is only called for the first open/up to initialize the device.
shutdown is called before each regular HCI close/down to perform vendor 
HCI epilog.

The Intel shutdown procedure consist in sending the 0xfc3f command which 
seems
to cause an internal reset with old firmwares (LED off with new one).
So, we need to HCI reset the controller before any other command in 
order to avoid
the "number of completed commands" issue.
To be sure that this HCI reset will be perform, I just put the HCI reset 
after the 0xfc3f
in the shutdown callback.

Since I only have old version, I can only test that the problem is fixed 
for me but not that
no regression is caused with the new fw/hw version.
So we need feedback, to know if the expected behavior (LED OFF on 
shutdown) is preserved.

Regards,
Loic

-- 
Intel Open Source Technology Center
http://oss.intel.com/

  reply	other threads:[~2015-06-08  8:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 14:35 [PATCHv2] Bluetooth: btusb: Fix Intel controller hang after shutdown Loic Poulain
2015-05-21 19:56 ` Marcel Holtmann
2015-06-04 11:59   ` Loic Poulain
2015-06-04 19:55     ` An, Tedd
2015-06-08  7:42       ` Ge, Ethan
2015-06-08  7:48         ` Ge, Ethan
2015-06-08  8:45           ` Loic Poulain [this message]
2015-06-08 18:18       ` Tedd Ho-Jeong An

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=55755617.8080302@intel.com \
    --to=loic.poulain@intel.com \
    --cc=ethan.ge@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=tedd.an@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.