summaryrefslogtreecommitdiffstats
path: root/net/bluetooth
diff options
context:
space:
mode:
authorMarcel Holtmann <marcel@holtmann.org>2014-09-14 23:06:28 +0200
committerJohan Hedberg <johan.hedberg@intel.com>2014-09-15 07:15:45 +0300
commit43e73e4e2ad05d9bf3b438cfbe1e71b57a85f26c (patch)
treef2f71821f7eec594de5123f42534499b0b97a09b /net/bluetooth
parent7cb9d20fd9f8fb41f29e294734c4f8b5dc81ed93 (diff)
downloadop-kernel-dev-43e73e4e2ad05d9bf3b438cfbe1e71b57a85f26c.zip
op-kernel-dev-43e73e4e2ad05d9bf3b438cfbe1e71b57a85f26c.tar.gz
Bluetooth: Provide HCI command opcode information to driver
The Bluetooth core already does processing of the HCI command header and puts it together before sending it to the driver. It is not really efficient for the driver to look at the HCI command header again in case it has to make certain decisions about certain commands. To make this easier, just provide the opcode as part of the SKB control buffer information. The extra information about the opcode is optional and only provided for HCI commands. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Diffstat (limited to 'net/bluetooth')
-rw-r--r--net/bluetooth/hci_core.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/net/bluetooth/hci_core.c b/net/bluetooth/hci_core.c
index 067526d..4194867 100644
--- a/net/bluetooth/hci_core.c
+++ b/net/bluetooth/hci_core.c
@@ -4547,6 +4547,7 @@ static struct sk_buff *hci_prepare_cmd(struct hci_dev *hdev, u16 opcode,
BT_DBG("skb len %d", skb->len);
bt_cb(skb)->pkt_type = HCI_COMMAND_PKT;
+ bt_cb(skb)->opcode = opcode;
return skb;
}
OpenPOWER on IntegriCloud