<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/include/net/bluetooth, branch v3.8</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/include/net/bluetooth?h=v3.8</id>
<link rel='self' href='https://git.amat.us/linux/atom/include/net/bluetooth?h=v3.8'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2012-12-03T18:00:01Z</updated>
<entry>
<title>Bluetooth: trivial: Change NO_FCS_RECV to RECV_NO_FCS</title>
<updated>2012-12-03T18:00:01Z</updated>
<author>
<name>Andrei Emeltchenko</name>
<email>andrei.emeltchenko@intel.com</email>
</author>
<published>2012-11-29T15:46:08Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f2592d3ee3c5817981f343b90bfb9c5612f38d23'/>
<id>urn:sha1:f2592d3ee3c5817981f343b90bfb9c5612f38d23</id>
<content type='text'>
Make code more readable by changing CONF_NO_FCS_RECV which is read
as "No L2CAP FCS option received" to CONF_RECV_NO_FCS which means
"Received L2CAP option NO_FCS". This flag really means that we have
received L2CAP FRAME CHECK SEQUENCE (FCS) OPTION with value "No FCS".

Signed-off-by: Andrei Emeltchenko &lt;andrei.emeltchenko@intel.com&gt;
Signed-off-by: Gustavo Padovan &lt;gustavo.padovan@collabora.co.uk&gt;
</content>
</entry>
<entry>
<title>Bluetooth: AMP: Check that AMP is present and active</title>
<updated>2012-12-03T18:00:00Z</updated>
<author>
<name>Andrei Emeltchenko</name>
<email>andrei.emeltchenko@intel.com</email>
</author>
<published>2012-11-29T15:46:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5d05416e0907b0dd30b62b002bed3b85e6efbd61'/>
<id>urn:sha1:5d05416e0907b0dd30b62b002bed3b85e6efbd61</id>
<content type='text'>
Before starting quering remote AMP controllers make sure
that there is local active AMP controller.

Signed-off-by: Andrei Emeltchenko &lt;andrei.emeltchenko@intel.com&gt;
Signed-off-by: Gustavo Padovan &lt;gustavo.padovan@collabora.co.uk&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Move double negation to macros</title>
<updated>2012-12-03T17:59:59Z</updated>
<author>
<name>Gustavo Padovan</name>
<email>gustavo.padovan@collabora.co.uk</email>
</author>
<published>2012-11-23T18:50:51Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ffa88e02bc67a1496fae762ad899e8f49136e7a1'/>
<id>urn:sha1:ffa88e02bc67a1496fae762ad899e8f49136e7a1</id>
<content type='text'>
Some comparisons needs to double negation(!!) in order to make the value
of the field boolean. Add it to the macro makes the code more readable.

Signed-off-by: Gustavo Padovan &lt;gustavo.padovan@collabora.co.uk&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Implement deferred sco socket setup</title>
<updated>2012-12-03T17:59:58Z</updated>
<author>
<name>Frédéric Dalleau</name>
<email>frederic.dalleau@linux.intel.com</email>
</author>
<published>2012-11-21T09:51:12Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=20714bfef84d3e690c9c6f8e9cd46543b5ae1eed'/>
<id>urn:sha1:20714bfef84d3e690c9c6f8e9cd46543b5ae1eed</id>
<content type='text'>
In order to authenticate and configure an incoming SCO connection, the
BT_DEFER_SETUP option was added. This option is intended to defer reply
to Connect Request on SCO sockets.
When a connection is requested, the listening socket is unblocked but
the effective connection setup happens only on first recv. Any send
between accept and recv fails with -ENOTCONN.

Signed-off-by: Frédéric Dalleau &lt;frederic.dalleau@linux.intel.com&gt;
Signed-off-by: Gustavo Padovan &lt;gustavo.padovan@collabora.co.uk&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Increase HCI command tx timeout</title>
<updated>2012-11-19T21:54:38Z</updated>
<author>
<name>Szymon Janc</name>
<email>szymon.janc@tieto.com</email>
</author>
<published>2012-11-12T10:01:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d1244adc4281eb983a7f41b753164233a7b16b55'/>
<id>urn:sha1:d1244adc4281eb983a7f41b753164233a7b16b55</id>
<content type='text'>
Read Local OOB Data command can take more than 1 second on some chips.
e.g. on CSR 0a12:0001 first call to Read Local OOB Data after reset
takes about 1300ms resulting in tx timeout error.

[27698.368655] Bluetooth: hci0 command 0x0c57 tx timeout

2012-10-31 15:53:36.178585 &lt; HCI Command: Read Local OOB Data (0x03|0x0057) plen 0
2012-10-31 15:53:37.496996 &gt; HCI Event: Command Complete (0x0e) plen 36
    Read Local OOB Data (0x03|0x0057) ncmd 1
    status 0x00
    hash 0x92219d9b447f2aa9dc12dda2ae7bae6a
    randomizer 0xb1948d0febe4ea38ce85c4e66313beba

Signed-off-by: Szymon Janc &lt;szymon.janc@tieto.com&gt;
Signed-off-by: Gustavo Padovan &lt;gustavo.padovan@collabora.co.uk&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Refactor locking in amp_physical_cfm</title>
<updated>2012-11-19T21:30:00Z</updated>
<author>
<name>Andrei Emeltchenko</name>
<email>andrei.emeltchenko@intel.com</email>
</author>
<published>2012-11-14T15:39:30Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a514b17fab51c1433db920d76cf8ddda959e5da0'/>
<id>urn:sha1:a514b17fab51c1433db920d76cf8ddda959e5da0</id>
<content type='text'>
Remove locking from l2cap_physical_cfm and lock chan inside
amp_physical_cfm.

Signed-off-by: Andrei Emeltchenko &lt;andrei.emeltchenko@intel.com&gt;
Acked-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Gustavo Padovan &lt;gustavo.padovan@collabora.co.uk&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Fix updating advertising state flags and data</title>
<updated>2012-11-19T01:03:01Z</updated>
<author>
<name>Johan Hedberg</name>
<email>johan.hedberg@intel.com</email>
</author>
<published>2012-11-08T00:23:01Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c1d5dc4ac15be45c7061e207f06ad8dfba0c2170'/>
<id>urn:sha1:c1d5dc4ac15be45c7061e207f06ad8dfba0c2170</id>
<content type='text'>
This patch adds a callback for the HCI_LE_Set_Advertise_Enable command.
The callback is responsible for updating the HCI_LE_PERIPHERAL flag
updating as well as updating the advertising data flags field to
indicate undirected connectable advertising.

Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
Acked-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Gustavo Padovan &lt;gustavo.padovan@collabora.co.uk&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Add support for setting LE advertising data</title>
<updated>2012-11-19T01:03:01Z</updated>
<author>
<name>Johan Hedberg</name>
<email>johan.hedberg@intel.com</email>
</author>
<published>2012-11-08T00:23:00Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3f0f524bafcd2025c12e215f13207c7be0a13bf9'/>
<id>urn:sha1:3f0f524bafcd2025c12e215f13207c7be0a13bf9</id>
<content type='text'>
This patch adds support for setting basing LE advertising data. The
three elements supported for now are the advertising flags, the TX power
and the friendly name.

Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
Acked-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Gustavo Padovan &lt;gustavo.padovan@collabora.co.uk&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Use proper invalid value for tx_power</title>
<updated>2012-11-19T01:03:00Z</updated>
<author>
<name>Johan Hedberg</name>
<email>johan.hedberg@intel.com</email>
</author>
<published>2012-11-08T00:22:59Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=bbaf444a89dd7dd7effd8ed2f4e4ec64da3cc1da'/>
<id>urn:sha1:bbaf444a89dd7dd7effd8ed2f4e4ec64da3cc1da</id>
<content type='text'>
The core specification defines 127 as the "not available" value (well,
"reserved" for BR/EDR and "not available" for LE - but essentially the
same). Therefore, instead of testing for 0 (which is in fact a valid
value) we should be using this invalid value to test if the tx_power is
available.

Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
Acked-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Gustavo Padovan &lt;gustavo.padovan@collabora.co.uk&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Fix parameter order of hci_get_route</title>
<updated>2012-11-01T22:27:11Z</updated>
<author>
<name>Johan Hedberg</name>
<email>johan.hedberg@intel.com</email>
</author>
<published>2012-11-01T11:27:26Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0c0afedf55ff409be9db0b0aeeaa1c6fe0f3cd3c'/>
<id>urn:sha1:0c0afedf55ff409be9db0b0aeeaa1c6fe0f3cd3c</id>
<content type='text'>
The actual parameter order of hci_get_route is (dst, src) and not (src,
dst). All current callers use the right order but the header file shows
the parameters in the wrong order.

Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
Signed-off-by: Gustavo Padovan &lt;gustavo.padovan@collabora.co.uk&gt;
</content>
</entry>
</feed>
