From: Loic Poulain <loic.poulain@intel.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Johan Hedberg <johan.hedberg@gmail.com>, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_uart: Introduce Intel HCI UART driver
Date: Mon, 06 Jul 2015 10:15:20 +0200 [thread overview]
Message-ID: <559A3918.803@intel.com> (raw)
In-Reply-To: <188DA073-D50B-4173-B879-0AFD8A0C7915@holtmann.org>
Hi Marcel,
> I did apply this patch to bluetooth-next tree, but I had to fix a bunch of coding style mistakes.
>
> Initially I was going to send this back, but in the end they were so easy to fix inline that it would have just delayed the process for getting larger exposure of this patch. However please review these since there were obvious coding style mistakes.
Thanks for the reviewing, fixing and testing of this patch.
It's obvious that my commit message was too poor, sorry for that.
> In addition, I did a test run on one of my development boards and having to wait almost 1 minute for the firmware to load is impressive. Seems we really want to add the higher speed UART support.
Regarding firmware download, with the 115200 default speed, I obtain the
same result (>1min)
Patch is ongoing to use the final speed. Using 3M, firmware download
takes about 4s.
> [171933.957748] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 34 2014
> [171933.969914] Bluetooth: hci0: Device revision is 5
> [171933.969916] Bluetooth: hci0: Secure boot is enabled
> [171933.969918] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
> [171933.969918] Bluetooth: hci0: No device address configured
> [171933.975503] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
> [171988.683798] Bluetooth: hci0: Waiting for firmware download to complete
> [171988.683801] Bluetooth: hci0: Firmware loaded in 53497399 usecs
> [171988.683886] Bluetooth: hci0: Waiting for device to boot
> [171988.696706] Bluetooth: hci0: Device booted in 12593 usecs
> [171988.714708] Bluetooth: hci0 hardware error 0x0e
I don't know why you get this hardware error, maybe a Intel reset param
issue with your device.
Thanks & Regards,
Loic
--
Intel Open Source Technology Center
http://oss.intel.com/
prev parent reply other threads:[~2015-07-06 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 10:20 [PATCH] Bluetooth: hci_uart: Introduce Intel HCI UART driver Loic Poulain
2015-07-04 13:15 ` Marcel Holtmann
2015-07-06 8:15 ` Loic Poulain [this message]
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=559A3918.803@intel.com \
--to=loic.poulain@intel.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
/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.