diff options
| author | Andre Guedes <andre.guedes@openbossa.org> | 2012-05-31 17:01:33 -0300 |
|---|---|---|
| committer | Johan Hedberg <johan.hedberg@intel.com> | 2012-06-05 06:34:15 +0300 |
| commit | 6fcb06a28d150095f042c477fbe20a9767d9a951 (patch) | |
| tree | 2432bb66eb04596105c677a75620334f42b7b4cd /net/bluetooth/l2cap_sock.c | |
| parent | 4f72b3291c9537a3c3c94552e248eaed8e4f8492 (diff) | |
| download | blackbird-op-linux-6fcb06a28d150095f042c477fbe20a9767d9a951.tar.gz blackbird-op-linux-6fcb06a28d150095f042c477fbe20a9767d9a951.zip | |
Bluetooth: Change default MTU for L2CAP ATT channel
This patch changes the default MTU value for L2CAP ATT fixed channel
to L2CAP_DEFAULT_MTU (672 octets).
Differently from others L2CAP channels, in L2CAP ATT fixed channel
there is no MTU negotiation. The MTU value for that channel is up to
the L2CAP implementation. The only restriction in L2CAP spec is the
MTU value must not be less than 23 octets.
At ATT protocol level (on top of L2CAP), we have the ATT_MTU which
defines the maximum size of any ATT message sent between client and
server. GATT profile defines ATT_MTU default value to 23 octets. If
a GATT based profile wants to use ATT_MTU greater than 23 octets
(e.g. HID over GATT profile), it should negotiate a new value by
executing the GATT Exchange MTU sub-procedure.
Thus, in order to support any value of ATT_MTU negotiated at ATT
protocol level, our L2CAP implementation should have L2CAP ATT
fixed channel MTU equal or greater than ATT_MAX_MTU (512 octets).
Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Diffstat (limited to 'net/bluetooth/l2cap_sock.c')
0 files changed, 0 insertions, 0 deletions
