Searched hist:"43 e73e4e2ad05d9bf3b438cfbe1e71b57a85f26c" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/include/net/bluetooth/ |
| H A D | bluetooth.h | diff 43e73e4e2ad05d9bf3b438cfbe1e71b57a85f26c Sun Sep 14 16:06:28 CDT 2014 Marcel Holtmann <marcel@holtmann.org> 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>
|
| /openbmc/linux/net/bluetooth/ |
| H A D | hci_core.c | diff 43e73e4e2ad05d9bf3b438cfbe1e71b57a85f26c Sun Sep 14 16:06:28 CDT 2014 Marcel Holtmann <marcel@holtmann.org> 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>
|