summaryrefslogtreecommitdiffstats
path: root/net/bluetooth/bnep/core.c
diff options
context:
space:
mode:
authorGrzegorz Kolodziejczyk <grzegorz.kolodziejczyk@tieto.com>2015-04-03 12:14:53 +0200
committerMarcel Holtmann <marcel@holtmann.org>2015-04-03 23:21:34 +0200
commit0477e2e868ceead7fd96218e1a062e01631ce717 (patch)
tree5cb7742c00b68c76b9f048d5d3fa7b9bb6c1f87b /net/bluetooth/bnep/core.c
parente0fdbab1699b89a9b0c192d4cb355f8ab43a8f17 (diff)
downloadtalos-obmc-linux-0477e2e868ceead7fd96218e1a062e01631ce717.tar.gz
talos-obmc-linux-0477e2e868ceead7fd96218e1a062e01631ce717.zip
Bluetooth: bnep: Add support for get bnep features via ioctl
This is needed if user space wants to know supported bnep features by kernel, e.g. if kernel supports sending response to bnep setup control message. By now there is no possibility to know supported features by kernel in case of bnep. Ioctls allows only to add connection, delete connection, get connection list, get connection info. Adding connection if it's possible (establishing network device connection) is equivalent to starting bnep session. Bnep session handles data queue of transmit, receive messages over bnep channel. It means that if we add connection the received/transmitted data will be parsed immediately. In case of get bnep features we want to know before session start, if we should leave setup data on socket queue and let kernel to handle with it, or in case of no setup handling support, if we should pull this message and handle setup response within user space. Signed-off-by: Grzegorz Kolodziejczyk <grzegorz.kolodziejczyk@tieto.com> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'net/bluetooth/bnep/core.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud