Commit 43e73e4e authored Sep 14, 2014 by Marcel Holtmann Committed by Johan Hedberg Sep 15, 2014

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>

parent 7cb9d20f

include/net/bluetooth/bluetooth.h

+1 −0

Original line number	Diff line number	Diff line
		@@ -284,6 +284,7 @@ struct hci_req_ctrl {
		struct bt_skb_cb {
		__u8 pkt_type;
		__u8 incoming;
		__u16 opcode;
		__u16 expect;
		__u8 force_active;
		struct l2cap_chan *chan;

net/bluetooth/hci_core.c

+1 −0

Original line number	Diff line number	Diff line
		@@ -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;
		}

Admin message