linux.git/drivers/bluetooth, branch v4.1-rc2 Linux kernel source tree Bluetooth: btusb: Use proper data structures for Intel vendor events 2015-04-09T07:42:18+00:00 Marcel Holtmann marcel@holtmann.org 2015-04-09T07:35:19+00:00 ccd6da2ab81815e03c0713069597a8fc8f6f8431 The Intel vendors events indicating firmware loading result and the bootup of the operational firmware are currently hardcoded byte comparisons. So intead of doing that, provide proper data structures and actually use them. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> 
The Intel vendors events indicating firmware loading result and the
bootup of the operational firmware are currently hardcoded byte
comparisons. So intead of doing that, provide proper data structures
and actually use them.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Bluetooth: hci_uart: Use generic Intel support for address setting 2015-04-07T16:48:21+00:00 Marcel Holtmann marcel@holtmann.org 2015-04-06T07:52:14+00:00 bca03c959ab377010d87bef2679890a4a4e66e37 The Bluetooth address setting for Intel devices is provided by a generic module now. Start using that module instead of relying it being included in the driver. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> 
The Bluetooth address setting for Intel devices is provided by a generic
module now. Start using that module instead of relying it being included
in the driver.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Bluetooth: btusb: Move Intel command structs into its own header 2015-04-07T16:48:21+00:00 Marcel Holtmann marcel@holtmann.org 2015-04-06T07:52:13+00:00 59a077c4792e2226b8a95430c0f17d1098939647 Since the Intel Bluetooth support has its own header, it makes sense to move all command structs into it. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> 
Since the Intel Bluetooth support has its own header, it makes sense
to move all command structs into it.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Bluetooth: btusb: Use generic Intel support for address support 2015-04-07T16:48:21+00:00 Marcel Holtmann marcel@holtmann.org 2015-04-06T07:52:12+00:00 4185a0f5d0431bf91ea1ec202fdf12e6e3b73c46 The Bluetooth address handling for Intel devices is provided by a generic module now. Start using that module instead of relying it being included in the driver. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> 
The Bluetooth address handling for Intel devices is provided by a generic
module now. Start using that module instead of relying it being included
in the driver.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Bluetooth: btintel: Introduce generic Intel Bluetooth support 2015-04-07T16:48:21+00:00 Marcel Holtmann marcel@holtmann.org 2015-04-06T07:52:11+00:00 48f0ed1bb68589db5d6566bd3cd28ec675feaf2f The majority of Intel Bluetooth vendor commands are shared between USB and UART transports. This creates a separate module that eventually will hold all Intel specific commands, but for now just start with the commands to change the Bluetooth public address and check for the default address. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> 
The majority of Intel Bluetooth vendor commands are shared between USB
and UART transports. This creates a separate module that eventually
will hold all Intel specific commands, but for now just start with the
commands to change the Bluetooth public address and check for the
default address.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Bluetooth: hci_uart: Provide generic H:4 receive framework 2015-04-07T16:48:21+00:00 Marcel Holtmann marcel@holtmann.org 2015-04-06T06:44:59+00:00 79b8df9362e8bd1951e1fddbd65ca87af8df52c8 Future H:4 based UART drivers require custom packet types and custom receive functions. To support this, extended the h4_recv_buf function with a packet definition table. For the default H:4 packets types of ACL data, SCO data and events, provide helpers to reduce the amount of code duplication. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> 
Future H:4 based UART drivers require custom packet types and custom
receive functions. To support this, extended the h4_recv_buf function
with a packet definition table.

For the default H:4 packets types of ACL data, SCO data and events,
provide helpers to reduce the amount of code duplication.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Bluetooth: btbcm: Add firmware table for UART based devices 2015-04-07T16:47:45+00:00 Marcel Holtmann marcel@holtmann.org 2015-04-06T05:52:19+00:00 9a0bb57d2d08f1923aeef3af1877ec0b6f3209ba The Broadcom UART based devices seem to use a little bit different firmare naming prefix. So add a separate table for these devices. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> 
The Broadcom UART based devices seem to use a little bit different
firmare naming prefix. So add a separate table for these devices.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Bluetooth: hci_uart: Add protocol support for Broadcom UART devices 2015-04-07T16:47:12+00:00 Marcel Holtmann marcel@holtmann.org 2015-04-06T05:52:18+00:00 bdd8818e05da187cd028f64ef2c0a2a6a582bcb1 This adds the protocol support for Broadcom based UART devices to enable firmware and patchram download procedure. It is a pretty straight forward H:4 driver with the exception of actually having its own setup and address configuration callbacks. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> 
This adds the protocol support for Broadcom based UART devices to
enable firmware and patchram download procedure. It is a pretty
straight forward H:4 driver with the exception of actually having
its own setup and address configuration callbacks.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Bluetooth: hci_uart: Move setup callback into different location 2015-04-07T16:47:11+00:00 Marcel Holtmann marcel@holtmann.org 2015-04-06T05:52:17+00:00 6ae4fddf78c11dedfb13a518a9050e9b265529ca The setup callback got wrongly inserted between the enqueue and dequeue callbacks. Move it to a better location. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> 
The setup callback got wrongly inserted between the enqueue and dequeue
callbacks. Move it to a better location.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Bluetooth: btusb: Update version number of the module 2015-04-07T16:47:11+00:00 Marcel Holtmann marcel@holtmann.org 2015-04-06T05:52:16+00:00 34dced9bd6baf677fa6cfbfb65f002601a10d1e7 The version number is cosmetic, but pretty handy for debugging purposes and since the Broadcom protocol support is now optional, just increase it to indicate the difference. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> 
The version number is cosmetic, but pretty handy for debugging purposes
and since the Broadcom protocol support is now optional, just increase
it to indicate the difference.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>