<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/include/net/bluetooth/hci.h, branch linux-3.19.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.19.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.19.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2014-12-05T16:15:33Z</updated>
<entry>
<title>Bluetooth: Enabled LE Direct Advertising Report event if supported</title>
<updated>2014-12-05T16:15:33Z</updated>
<author>
<name>Marcel Holtmann</name>
</author>
<published>2014-12-05T15:20:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4b71bba45c420065044bf040b2284893ab900d03'/>
<id>urn:sha1:4b71bba45c420065044bf040b2284893ab900d03</id>
<content type='text'>
When the controller supports the Extended Scanner Filter Policies, it
supports the LE Direct Advertising Report event. However by default
that event is blocked by the LE event mask. It is required to enable
it during controller setup.

Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Add definitions for LE Direct Advertising Report event</title>
<updated>2014-12-05T16:15:18Z</updated>
<author>
<name>Marcel Holtmann</name>
</author>
<published>2014-12-05T15:20:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=32c9d43fa5deac40eee5a689428367982f147044'/>
<id>urn:sha1:32c9d43fa5deac40eee5a689428367982f147044</id>
<content type='text'>
This patch adds the event id and data structures for the LE Direct
Advertising Report event.

Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Move LE advertising report defines to the right location</title>
<updated>2014-12-05T16:15:02Z</updated>
<author>
<name>Marcel Holtmann</name>
</author>
<published>2014-12-05T15:20:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2331fd46f5452944f32a2bc78fa05026617887c6'/>
<id>urn:sha1:2331fd46f5452944f32a2bc78fa05026617887c6</id>
<content type='text'>
All Bluetooth commands and events are ordered by its opcode or event
id, but for some reason this one now stands out. So move it to its
correct spot in the list.

Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Add HCI_RSSI_INVALID for unknown RSSI value</title>
<updated>2014-12-05T10:37:30Z</updated>
<author>
<name>Marcel Holtmann</name>
</author>
<published>2014-12-05T09:55:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a89612aac3cc6b13e6738bd70e05faf6f3fc8d9e'/>
<id>urn:sha1:a89612aac3cc6b13e6738bd70e05faf6f3fc8d9e</id>
<content type='text'>
The Bluetooth core specification defines the value 127 as invalid for
RSSI values. So instead of hard coding it, lets add a constant for it.

Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Add debugfs switch for forcing SMP over BR/EDR</title>
<updated>2014-12-03T15:51:20Z</updated>
<author>
<name>Johan Hedberg</name>
</author>
<published>2014-10-16T08:45:31Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=858cdc78be8be19b7176cafe06d3db3acfb345d4'/>
<id>urn:sha1:858cdc78be8be19b7176cafe06d3db3acfb345d4</id>
<content type='text'>
To make it possible to use LE SC functionality over BR/EDR with pre-4.1
controllers (that do not support BR/EDR SC links) it's useful to be able
to force LE SC operations even over a traditional SSP protected link.
This patch adds a debugfs switch to force a special debug flag which is
used to skip the checks for BR/EDR SC support.

Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Use shorter "rand" name for "randomizer"</title>
<updated>2014-11-18T00:53:15Z</updated>
<author>
<name>Johan Hedberg</name>
</author>
<published>2014-11-17T18:52:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=38da1703060a520e69b00405f9bdf765d1396cd0'/>
<id>urn:sha1:38da1703060a520e69b00405f9bdf765d1396cd0</id>
<content type='text'>
The common short form of "randomizer" is "rand" in many places
(including the Bluetooth specification). The shorter version also makes
for easier to read code with less forced line breaks. This patch renames
all occurences of "randomizer" to "rand" in the Bluetooth subsystem
code.

Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Add hci_conn_lookup_type() helper function</title>
<updated>2014-11-03T08:13:43Z</updated>
<author>
<name>Marcel Holtmann</name>
</author>
<published>2014-11-03T04:16:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=845472e8d50c898c73b4f69f4edad5249b13d6a9'/>
<id>urn:sha1:845472e8d50c898c73b4f69f4edad5249b13d6a9</id>
<content type='text'>
Some drivers require knowledge of what connection handle is assigned
to what connection link type (ACL or SCO/eSCO). Instead of having each
driver implement connection tracking, provide a simple helper function
for lookup of the link type.

Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Introduce HCI_QUIRK_STRICT_DUPLICATE_FILTER</title>
<updated>2014-11-03T08:13:36Z</updated>
<author>
<name>Marcel Holtmann</name>
</author>
<published>2014-11-02T19:52:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=43d6bc46e2d342204693d24ce1c607305d93d8fb'/>
<id>urn:sha1:43d6bc46e2d342204693d24ce1c607305d93d8fb</id>
<content type='text'>
Some vendors decide to use a strict duplicate filter policy that only
filters on Bluetooth device addresses. This means that when the RSSI
changes, these devices are not reported again. During discovery it is
useful to actually get the RSSI updates.

Since this is specific to each controller, add a new quirk setting
that allows drivers to tell the core what kind of filtering policy
the controller uses.

Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Print error message for HCI_Hardware_Error event</title>
<updated>2014-11-02T07:59:42Z</updated>
<author>
<name>Marcel Holtmann</name>
</author>
<published>2014-11-02T01:56:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=24dfa343716a493472db0555342bb88678efa444'/>
<id>urn:sha1:24dfa343716a493472db0555342bb88678efa444</id>
<content type='text'>
When the HCI_Hardware_Error event is send by the controller or
injected by the driver, then at least print an error message.

Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Fix reason code used for rejecting SCO connections</title>
<updated>2014-09-24T12:03:32Z</updated>
<author>
<name>Johan Hedberg</name>
</author>
<published>2014-09-24T10:14:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d41c15cf95bd91b9c333f6f749670e22c8a47ad9'/>
<id>urn:sha1:d41c15cf95bd91b9c333f6f749670e22c8a47ad9</id>
<content type='text'>
The core specification defines valid values for the
HCI_Reject_Synchronous_Connection_Request command to be 0x0D-0x0F. So
far the code has been using HCI_ERROR_REMOTE_USER_TERM (0x13) which is
not a valid value and is therefore being rejected by some controllers:

 &gt; HCI Event: Connect Request (0x04) plen 10
	bdaddr 40:6F:2A:6A:E5:E0 class 0x000000 type eSCO
 &lt; HCI Command: Reject Synchronous Connection (0x01|0x002a) plen 7
	bdaddr 40:6F:2A:6A:E5:E0 reason 0x13
	Reason: Remote User Terminated Connection
 &gt; HCI Event: Command Status (0x0f) plen 4
	Reject Synchronous Connection (0x01|0x002a) status 0x12 ncmd 1
	Error: Invalid HCI Command Parameters

This patch introduces a new define for a value from the valid range
(0x0d == Connection Rejected Due To Limited Resources) and uses it
instead for rejecting incoming connections.

Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
</feed>
