<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/net/bluetooth/mgmt.c, branch linux-3.13.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.13.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.13.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2013-10-21T14:18:27Z</updated>
<entry>
<title>Bluetooth: Fix enabling fast connectable on LE-only controllers</title>
<updated>2013-10-21T14:18:27Z</updated>
<author>
<name>Johan Hedberg</name>
</author>
<published>2013-10-21T13:51:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=547003b114bcb96555cf73ec7f45ab64b2dcaf67'/>
<id>urn:sha1:547003b114bcb96555cf73ec7f45ab64b2dcaf67</id>
<content type='text'>
The current "fast connectable" feature is BR/EDR-only, so add a proper
check for BR/EDR support before proceeding with the associated HCI
commands.

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: Update Set Discoverable to support LE</title>
<updated>2013-10-20T16:05:41Z</updated>
<author>
<name>Johan Hedberg</name>
</author>
<published>2013-10-20T16:00:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9a43e25fff07a94f40d4a9e1081458e30c840256'/>
<id>urn:sha1:9a43e25fff07a94f40d4a9e1081458e30c840256</id>
<content type='text'>
This patch updates the Set Discoverable management command to also be
applicable for LE. In particular this affects the advertising flags
where we can say "general discoverable" or "limited discoverable".

Since the device flags may not be up-to-date when the advertising data
is written this patch introduces a get_adv_discov_flags() helper
function which also looks at any pending mgmt commands (a pending
set_discoverable would be the exception when the flags are not yet
correct).

The patch also adds HCI_DISCOVERABLE flag clearing to the
mgmt_discoverable_timeout function, since the code was previously
relying on the mgmt_discoverable callback to handle this, which is only
called for the BR/EDR-only HCI_Write_Scan_Enable command.

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: Move HCI_LIMITED_DISCOVERABLE changes to a general place</title>
<updated>2013-10-20T16:05:41Z</updated>
<author>
<name>Johan Hedberg</name>
</author>
<published>2013-10-19T20:38:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b456f87cb0c726cf97ce1e88aecfcbacf1cdf5fe'/>
<id>urn:sha1:b456f87cb0c726cf97ce1e88aecfcbacf1cdf5fe</id>
<content type='text'>
We'll soon be introducing also LE support for the Set Discoverable
management command, so move the HCI_LIMITED_DISCOVERABLE flag clearing
and setting out from the if-branch that is only used for a BR/EDR
specific HCI command.

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: Fix sending write_scan_enable when BR/EDR is disabled</title>
<updated>2013-10-20T16:05:40Z</updated>
<author>
<name>Johan Hedberg</name>
</author>
<published>2013-10-19T20:38:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4b580614e1435628490a1762726638546f3a5e4e'/>
<id>urn:sha1:4b580614e1435628490a1762726638546f3a5e4e</id>
<content type='text'>
We should only send the HCI_Write_Scan_Enable command from
mgmt_set_powered_failed() when BR/EDR support is enabled. This is
particularly important when the discoverable setting is also tied to LE.

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: Move mgmt_pending_find to avoid forward declarations</title>
<updated>2013-10-20T16:05:40Z</updated>
<author>
<name>Johan Hedberg</name>
</author>
<published>2013-10-19T20:38:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=eb2a8d202f91b874d5650c9e0a2c42fdaf137d91'/>
<id>urn:sha1:eb2a8d202f91b874d5650c9e0a2c42fdaf137d91</id>
<content type='text'>
We will soon need this function for updating the advertising data, so
move it higher up in mgmt.c to avoid a forward declaration.

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: Fix updating settings when there are no HCI commands to send</title>
<updated>2013-10-20T16:05:40Z</updated>
<author>
<name>Johan Hedberg</name>
</author>
<published>2013-10-19T20:38:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a81070ba3743400444275cc87f8f91bb5b67dd4b'/>
<id>urn:sha1:a81070ba3743400444275cc87f8f91bb5b67dd4b</id>
<content type='text'>
It is possible that the Set Connectable management command doesn't cause
any HCI commands to send (such as when BR/EDR is disabled). We can't
just send a response to user space in this case but must also update the
necessary device flags and settings. This patch fixes the issue by using
the recently introduced set_connectable_update_settings function.

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: Refactor set_connectable settings update to separate function</title>
<updated>2013-10-20T16:05:40Z</updated>
<author>
<name>Johan Hedberg</name>
</author>
<published>2013-10-19T20:38:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e8ba3a1f08d9386b6e4abe9b00c21e38029a76a4'/>
<id>urn:sha1:e8ba3a1f08d9386b6e4abe9b00c21e38029a76a4</id>
<content type='text'>
We will need to directly update the device flags and notify user space
of the new settings not just when we're powered off but also if it turns
out that there are no HCI commands to send (which can happen in
particular when BR/EDR is disabled). Since this is a considerable amount
of code, refactor it to a separate function so it can be reused for the
"no HCI commands to send" case.

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 missing check for BREDR_ENABLED flag in update_class()</title>
<updated>2013-10-20T16:05:40Z</updated>
<author>
<name>Johan Hedberg</name>
</author>
<published>2013-10-19T20:38:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f87ea1dabb4b0e50f0c3d7140d89f1bb697a1676'/>
<id>urn:sha1:f87ea1dabb4b0e50f0c3d7140d89f1bb697a1676</id>
<content type='text'>
We shouldn't be sending the HCI_Write_Class_Of_Device command when
BR/EDR is disabled since this is a BR/EDR-only command.

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: Check for flag instead of features in update_adv_data()</title>
<updated>2013-10-20T16:05:40Z</updated>
<author>
<name>Johan Hedberg</name>
</author>
<published>2013-10-19T20:38:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=10994ce6e6696d2fb5a14601302da9b680fc9cc9'/>
<id>urn:sha1:10994ce6e6696d2fb5a14601302da9b680fc9cc9</id>
<content type='text'>
It's better to check for the device flag instead of device features so
that we avoid unnecessary HCI commands when the feature is supported but
disabled (i.e. the flag is unset).

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: Check for flag instead of features in update_scan_rsp_data()</title>
<updated>2013-10-20T16:05:40Z</updated>
<author>
<name>Johan Hedberg</name>
</author>
<published>2013-10-19T20:38:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7751ef1b3184ecfaebc5e5a8981407814ce0be0b'/>
<id>urn:sha1:7751ef1b3184ecfaebc5e5a8981407814ce0be0b</id>
<content type='text'>
It's better to check for the device flag instead of device features so
that we avoid unnecessary HCI commands when the feature is supported but
disabled (i.e. the flag is unset).

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