summaryrefslogtreecommitdiffstats
path: root/drivers/bluetooth/btintel.h
diff options
context:
space:
mode:
authorMarcel Holtmann <marcel@holtmann.org>2015-04-09 00:35:19 -0700
committerJohan Hedberg <johan.hedberg@intel.com>2015-04-09 10:42:18 +0300
commitccd6da2ab81815e03c0713069597a8fc8f6f8431 (patch)
tree416bc259c99403c30add4fe0c1083e92c1134a37 /drivers/bluetooth/btintel.h
parent94910d419a506a8e21333cc87ffb80db8b89d88a (diff)
downloadlinux-ccd6da2ab81815e03c0713069597a8fc8f6f8431.tar.bz2
Bluetooth: btusb: Use proper data structures for Intel vendor events
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>
Diffstat (limited to 'drivers/bluetooth/btintel.h')
-rw-r--r--drivers/bluetooth/btintel.h15
1 files changed, 15 insertions, 0 deletions
diff --git a/drivers/bluetooth/btintel.h b/drivers/bluetooth/btintel.h
index d1581150679a..4bda6ab34f60 100644
--- a/drivers/bluetooth/btintel.h
+++ b/drivers/bluetooth/btintel.h
@@ -54,6 +54,21 @@ struct intel_boot_params {
__u8 unlocked_state;
} __packed;
+struct intel_bootup {
+ __u8 zero;
+ __u8 num_cmds;
+ __u8 source;
+ __u8 reset_type;
+ __u8 reset_reason;
+ __u8 ddc_status;
+} __packed;
+
+struct intel_secure_send_result {
+ __u8 result;
+ __le16 opcode;
+ __u8 status;
+} __packed;
+
#if IS_ENABLED(CONFIG_BT_INTEL)
int btintel_check_bdaddr(struct hci_dev *hdev);