<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/bluetooth, branch v2.6.29.1</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/bluetooth?h=v2.6.29.1</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/bluetooth?h=v2.6.29.1'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2008-11-30T11:17:28Z</updated>
<entry>
<title>Bluetooth: Enable per-module dynamic debug messages</title>
<updated>2008-11-30T11:17:28Z</updated>
<author>
<name>Marcel Holtmann</name>
<email>marcel@holtmann.org</email>
</author>
<published>2008-11-30T11:17:28Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a418b893a6af11ae73c762ed5b76c1bad6dc19d8'/>
<id>urn:sha1:a418b893a6af11ae73c762ed5b76c1bad6dc19d8</id>
<content type='text'>
With the introduction of CONFIG_DYNAMIC_PRINTK_DEBUG it is possible to
allow debugging without having to recompile the kernel. This patch turns
all BT_DBG() calls into pr_debug() to support dynamic debug messages.

As a side effect all CONFIG_BT_*_DEBUG statements are now removed and
some broken debug entries have been fixed.

Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Allow SCO audio with Asus WL-BTD202 dongle</title>
<updated>2008-11-30T11:17:27Z</updated>
<author>
<name>Marcel Holtmann</name>
<email>marcel@holtmann.org</email>
</author>
<published>2008-11-30T11:17:27Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5ddd4a60683f819982b7bd3d1aee972f931c11a3'/>
<id>urn:sha1:5ddd4a60683f819982b7bd3d1aee972f931c11a3</id>
<content type='text'>
This patch allows the Asus WL-BTD202 dongle to be used with a mono
headset without having to specify "options btusb force_scofix=1".

Based on a patch from Guillaume Bedot &lt;littletux@zarb.org&gt;

Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Send HCI Reset command by default on device initialization</title>
<updated>2008-11-30T11:17:26Z</updated>
<author>
<name>Marcel Holtmann</name>
<email>marcel@holtmann.org</email>
</author>
<published>2008-11-30T11:17:26Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7a9d4020533b5c0c615b6de3be154c9ff30b8cc9'/>
<id>urn:sha1:7a9d4020533b5c0c615b6de3be154c9ff30b8cc9</id>
<content type='text'>
The Bluetooth subsystem was not using the HCI Reset command when doing
device initialization. The Bluetooth 1.0b specification was ambiguous
on how the device firmware was suppose to handle it. Almost every device
was triggering a transport reset at the same time. In case of USB this
ended up in disconnects from the bus.

All modern Bluetooth dongles handle this perfectly fine and a lot of
them actually require that HCI Reset is sent. If not then they are
either stuck in their HID Proxy mode or their internal structures for
inquiry and paging are not correctly setup.

To handle old and new devices smoothly the Bluetooth subsystem contains
a quirk to force the HCI Reset on initialization. However maintaining
such a quirk becomes more and more complicated. This patch turns the
logic around and lets the old devices disable the HCI Reset command.

The only device where the HCI_QUIRK_NO_RESET is still needed are the
original Digianswer devices and dongles with an early CSR firmware.

CSR reported that they fixed this for version 12 firmware. The last
official release of version 11 firmware is build ID 115. The first
version 12 candidate was build ID 117.

Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Remove deprecated hci_usb driver</title>
<updated>2008-11-30T11:17:21Z</updated>
<author>
<name>Marcel Holtmann</name>
<email>marcel@holtmann.org</email>
</author>
<published>2008-11-30T11:17:21Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=12421b40b81d101d7535e03f1af197365adc932b'/>
<id>urn:sha1:12421b40b81d101d7535e03f1af197365adc932b</id>
<content type='text'>
The old hci_usb driver has been fully replaced with the new btusb driver
and all major distributions switched to the new driver now. This removes
it since it should not be used at all anymore.

Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Respect HCI_UART_DEBUG config in hci_ll.c</title>
<updated>2008-11-30T11:17:20Z</updated>
<author>
<name>Nick Pelly</name>
<email>npelly@google.com</email>
</author>
<published>2008-11-30T11:17:20Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7b99d17f3ea1febd1abca8fa371d2341dd957d4a'/>
<id>urn:sha1:7b99d17f3ea1febd1abca8fa371d2341dd957d4a</id>
<content type='text'>
Following the pattern from hci_*.c, turn off BT_DBG messages unless
they have been requested via HCI_UART_DEBUG

Signed-off-by: Nick Pelly &lt;npelly@google.com&gt;
Acked-by: Brian Swetland &lt;swetland@google.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Change simple_strtol to simple_strtoul</title>
<updated>2008-11-30T11:17:20Z</updated>
<author>
<name>Julia Lawall</name>
<email>julia@diku.dk</email>
</author>
<published>2008-11-30T11:17:20Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=51a6fbc855b07a0737558560dd0ab0b5f646025b'/>
<id>urn:sha1:51a6fbc855b07a0737558560dd0ab0b5f646025b</id>
<content type='text'>
Since size, addr, fcs, and tmp are unsigned, it would seem better to use
simple_strtoul that simple_strtol.

A simplified version of the semantic patch that makes this change is as
follows: (http://www.emn.fr/x-info/coccinelle/)

// &lt;smpl&gt;
@r2@
long e;
position p;
@@

e = simple_strtol@p(...)

@@
position p != r2.p;
type T;
T e;
@@

e =
- simple_strtol@p
+ simple_strtoul
  (...)
// &lt;/smpl&gt;

Signed-off-by: Julia Lawall &lt;julia@diku.dk&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Fix TX error path in btsdio driver</title>
<updated>2008-11-30T11:17:18Z</updated>
<author>
<name>Tomas Winkler</name>
<email>tomas.winkler@intel.com</email>
</author>
<published>2008-11-30T11:17:18Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7644d63d1348ec044ccd8f775fefe5eb7cbcac69'/>
<id>urn:sha1:7644d63d1348ec044ccd8f775fefe5eb7cbcac69</id>
<content type='text'>
This patch fixes accumulating of the header in case packet was requeued
in the error path.

Signed-off-by: Tomas Winkler &lt;tomas.winkler@intel.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Add suspend/resume support to btusb driver</title>
<updated>2008-11-30T11:17:14Z</updated>
<author>
<name>Marcel Holtmann</name>
<email>marcel@holtmann.org</email>
</author>
<published>2008-11-30T11:17:14Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6a88adf2adf5d6a3b759c2e114da4c5266ca3972'/>
<id>urn:sha1:6a88adf2adf5d6a3b759c2e114da4c5266ca3972</id>
<content type='text'>
During suspend it is important that all URBs are cancelled and then on
resume re-submitted. This gives initial suspend/resume support.

Based on initial work from Oliver Neukum &lt;oneukum@suse.de&gt;

Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Handle bulk URBs in btusb driver from notify callback</title>
<updated>2008-11-30T11:17:12Z</updated>
<author>
<name>Marcel Holtmann</name>
<email>marcel@holtmann.org</email>
</author>
<published>2008-11-30T11:17:12Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a780efa8124fe7ef23d8ef844d56afe960356615'/>
<id>urn:sha1:a780efa8124fe7ef23d8ef844d56afe960356615</id>
<content type='text'>
With the addition of usb_unlink_anchored_urbs() it is possible to fully
control the bulk URBs from the notify callback. There is no need to
schedule work and so only do this for the ISOC URBs.

Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Add fine grained mem_flags usage to btusb driver</title>
<updated>2008-11-30T11:17:10Z</updated>
<author>
<name>Marcel Holtmann</name>
<email>marcel@holtmann.org</email>
</author>
<published>2008-11-30T11:17:10Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2eda66f4a0b9803c6a85d5e5ccd8e802bd23b998'/>
<id>urn:sha1:2eda66f4a0b9803c6a85d5e5ccd8e802bd23b998</id>
<content type='text'>
The URB submission routines need more fine grained control for the
mem_flags used by kmalloc(), usb_alloc_urb() and usb_submit_urb() to
better support different caller situations. Add a mem_flags parameter
and give the caller full control.

Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
</feed>
