- 09 May, 2012 40 commits
-
-
Mat Martineau authored
Adds some missing values for control field parsing, additional data for the new state machine, and enumerations for states, incoming packet classification, and state machine events. Signed-off-by:
Mat Martineau <mathewm@codeaurora.org> Acked-by:
Marcel Holtmann <marcel@holtmann.org> Signed-off-by:
Gustavo Padovan <gustavo@padovan.org>
-
Andrei Emeltchenko authored
Add comments to timer implementation and style fixes. Signed-off-by:
Andrei Emeltchenko <andrei.emeltchenko@intel.com> Acked-by:
-
Andre Guedes authored
This patch adds the HCI_PERIODIC_INQ flag to dev_flags. This flag tracks if periodic inquiry is enabled or not. Signed-off-by:
Andre Guedes <aguedespe@gmail.com> Acked-by:
-
Andre Guedes authored
This patch adds a handler function to Periodic Inquiry command complete event. Signed-off-by:
-
Andre Guedes authored
This patch changes inquiry result function handlers so they ignore inquiry result events if periodic inquiry is enabled. Signed-off-by:
-
Andre Guedes authored
This patch adds a HCI_PERIODIC_INQ check to start_discovery. If periodic inquiry is enabled, we fail MGMT Start Discovery command with MGMT_STATUS_BUSY code. Signed-off-by:
-
Andre Guedes authored
This patch adds the HCI_PERIODIC_INQ flag to dev_flags. This flag tracks if periodic inquiry is enabled or not. Signed-off-by:
-
Andre Guedes authored
This patch adds a handler function to Periodic Inquiry command complete event. Signed-off-by:
-
Andre Guedes authored
This patch does a trivial code refactoring in stop_discovery function by using a switch statement instead of an if-return-else approach. Signed-off-by:
Andre Guedes <andre.guedes@openbossa.org> Acked-by:
-
Andre Guedes authored
We should return -EALREADY in hci_cancel_inquiry since it is more suitable than -EPERM error code. Signed-off-by:
-
Andrei Emeltchenko authored
Silence sparse warning shown below: ... net/bluetooth/mgmt.c:448:15: warning: cast to restricted __le32 ... Signed-off-by:
-
Szymon Janc authored
Reply with MGMT_STATUS_INVALID_PARAMS when userspace is trying to set source with out-of-scope value. Signed-off-by:
Szymon Janc <szymon.janc@tieto.com> Acked-by:
Johan Hedberg <johan.hedberg@intel.com>
-
Szymon Janc authored
Signed-off-by:
-
Andre Guedes authored
This patch adds LE support to MGMT stop discovery command. So, now we are able to cancel LE discovery procedures (LE-only and interleaved). Signed-off-by:
-
Andre Guedes authored
This patch adds to hci_core the hci_cancel_le_scan function which should be used to cancel an ongoing LE scan. Signed-off-by:
-
Andrei Emeltchenko authored
Fix sparse warnings related to incorrect type in assignment and static symbol. Also use const keyword. Warnings are shown below: ... net/bluetooth/mgmt.c:305:28: warning: incorrect type in assignment (different base types) net/bluetooth/mgmt.c:305:28: expected unsigned short [usertype] *opcode net/bluetooth/mgmt.c:305:28: got restricted __le16 *<noident> ... net/bluetooth/mgmt.c:2609:3: warning: symbol 'mgmt_handlers' was not declared. Should it be static? ... Signed-off-by:
-
Marcel Holtmann authored
In case the struct is already __packed, there is no need to use unaligned access to the data. So just use __le16_to_cpu in these cases. Signed-off-by:
-
Andrei Emeltchenko authored
opcode to be accessed is in le16 format so convert it first to cpu byte order. Signed-off-by:
-
Andrei Emeltchenko authored
Use struct hci_cp_write_def_link_policy to overcome sparse warnigs below: ... net/bluetooth/hci_event.c:633:21: warning: incorrect type in assignment (different base types) net/bluetooth/hci_event.c:633:21: expected unsigned short [unsigned] [assigned] [usertype] link_policy net/bluetooth/hci_event.c:633:21: got restricted __le16 [usertype] <noident> ... Signed-off-by:
-
Andrei Emeltchenko authored
Fix sparse warnigns below: ... net/bluetooth/hci_sysfs.c:458:33: warning: cast to restricted __be32 net/bluetooth/hci_sysfs.c:458:47: warning: cast to restricted __be16 ... Signed-off-by:
-
Andrei Emeltchenko authored
In L2CAP we use le16 format so change direction of conversion from le16_to_cpu to cpu_to_le16. Signed-off-by:
-
Andrei Emeltchenko authored
Create Chan Rsp shall put result and status in le format. Signed-off-by:
-
Andrei Emeltchenko authored
L2CAP channel id is used in host format in internal L2CAP code. Fix sparse warnings about wrong endian conversion. Signed-off-by:
-
Andrei Emeltchenko authored
cmd->len is in le format so convert it to host format before use. Signed-off-by:
-
Andrei Emeltchenko authored
ediv is already in little endian order. Signed-off-by:
-
Marcel Holtmann authored
In case the struct is already __packed, there is no need to use unaligned access to the data. So just use cpu_to_le16 or __constant_cpu_to_le16 in these cases. Signed-off-by:
-
Marcel Holtmann authored
The Device ID details need to be programmed into the kernel for every controller at least once. So provide management command for this. Signed-off-by:
-
Marcel Holtmann authored
The Device ID information can be provided via Extended Inquiry Data as well. If a valid source is present, then include it. Signed-off-by:
-
Marcel Holtmann authored
The Inquiry Response TX power tag should be added to the Extended Inquiry Data (EIR) as well. Signed-off-by:
-
David Herrmann authored
We initialize the "struct device" in hci_alloc_dev() for a long time now so we can access hdev->dev.parent directly. Hence, we can drop the temporary field hdev->parent which is used in no other place than hci_add_sysfs(). SET_HCIDEV_DEV() is never called after registering a device by the drivers so we do not overwrite internal device-state. Furthermore, hdev->dev is initialized to 0 by kzalloc() inside hci_alloc_dev() so the default behavior with dev.parent = NULL is kept. Signed-off-by:
David Herrmann <dh.herrmann@googlemail.com> Acked-by:
-
Andre Guedes authored
In order to do interleaved discovery we should be in DISCOVERY_ FINDING state. Otherwise, discovery should be stopped. Signed-off-by:
Gustavo F. Padovan <padovan@profusion.mobi>
-
Andrei Emeltchenko authored
chan->psm is kept in __le16 format which was not always taken into account. Fix several bugs related to extra conversion. Signed-off-by:
-
Andrei Emeltchenko authored
Value to be converted is already in __le32 format. Signed-off-by:
-
Andrei Emeltchenko authored
Correct type warnings reported by sparse to show that this functions takes ediv argument in __le16 format. Signed-off-by:
-
Andrei Emeltchenko authored
Keep lmp_subver in host byte order. We have following conversion in hci_cc_read_local_version: hdev->lmp_subver = __le16_to_cpu(rp->lmp_subver); Signed-off-by:
-
Andrei Emeltchenko authored
Correct endian conversion reported by sparse Signed-off-by:
-
John W. Linville authored
Signed-off-by:John W. Linville <linville@tuxdriver.com>
-
Ashok Nagarajan authored
This patch introduces a new mesh configuration parameter "ht_opmode" and will allow user to check the current HT protection mode selected. Users could configure the protection mode by the command "iw mesh_iface set mesh_param mesh_ht_protection_mode=2". The default protection mode of mesh is set to non-HT mixed mode. Signed-off-by:
Ashok Nagarajan <ashok@cozybit.com> Reviewed-by:
Thomas Pedersen <thomas@cozybit.com> Signed-off-by:
-
Ashok Nagarajan authored
Now that we have protection enabled, allow non-HT and HT20 stations to peer with HT40+/- stations. Peering is still disallowed for HT40+/- mismatch. Signed-off-by:
-
Ashok Nagarajan authored
Section 9.23.3.5 of IEEE 80211s standard describes the protection rules for HT mesh STA in a MBSS. Three HT protection modes are supported for now: non-HT mixed mode - is selected if any non-HT peers are present in our MBSS. 20MHz-protection mode - is selected if all peers in our 20/40MHz MBSS support HT and atleast one HT20 peer is present. no-protection mode - is selected otherwise. This is a limited implementation of 9.23.3.5, which only considers mesh peers when determining the HT protection mode. Station's channel_type needs to be maintained. Signed-off-by:
-
