linux-toradex.git/net/bluetooth/Kconfig, branch v3.10.45

Bluetooth: trivial: Remove newline before EOF

2012-10-24T02:42:47+00:00

Trivial fix.

Signed-off-by: Syam Sidhardhan 
Acked-by: Marcel Holtmann 
Signed-off-by: Gustavo Padovan

Bluetooth: AMP: Add AMP key calculation

2012-09-27T20:30:22+00:00

Function calculates AMP keys using hmac_sha256 helper. Calculated keys
are Generic AMP Link Key (gamp) and Dedicated AMP Link Key with
keyID "802b" for 802.11 PAL.

Signed-off-by: Andrei Emeltchenko 
Signed-off-by: Gustavo Padovan

Bluetooth: Fix Kconfig help description

2012-02-29T16:50:25+00:00

SMP is not a kernel module, it is part of Bluetooth Core (as already
described in lines above).

Signed-off-by: Andre Guedes 
Acked-by: Gustavo F. Padovan 
Acked-by: Marcel Holtmann 
Signed-off-by: Johan Hedberg

Bluetooth: Always compile SCO and L2CAP in Bluetooth Core

2011-12-21T04:21:08+00:00

The handling of SCO audio links and the L2CAP protocol are essential to
any system with Bluetooth thus are always compiled in from now on.

Signed-off-by: Ulisses Furquim 
Acked-by: Marcel Holtmann 
Signed-off-by: Gustavo F. Padovan

bluetooth: uses crypto interfaces, select CRYPTO

2011-06-27T19:09:39+00:00

Recent changes to hci_core.c use crypto interfaces, so select CRYPTO
to make sure that those interfaces are present.

Fixes these build errors when CRYPTO is not enabled:

net/built-in.o: In function `hci_register_dev':
(.text+0x4cf86): undefined reference to `crypto_alloc_base'
net/built-in.o: In function `hci_unregister_dev':
(.text+0x4f912): undefined reference to `crypto_destroy_tfm'

Signed-off-by: Randy Dunlap 
Signed-off-by: John W. Linville

Bluetooth: Add support for using the crypto subsystem

2011-06-13T18:48:22+00:00

This will allow using the crypto subsystem for encrypting data. As SMP
(Security Manager Protocol) is implemented almost entirely on the host
side and the crypto module already implements the needed methods
(AES-128), it makes sense to use it.

There's now a new module option to enable/disable SMP support.

Signed-off-by: Vinicius Costa Gomes 
Signed-off-by: Anderson Briglia 
Signed-off-by: Gustavo F. Padovan

Bluetooth: Fix BT_L2CAP and BT_SCO in Kconfig

2011-02-28T19:06:53+00:00

If we want something "bool" built-in in something "tristate" it can't
"depend on" the tristate config option.

Report by DaveM:

   I give it 'y' just to make it happen, for both, and afterways no
   matter how many times I rerun "make oldconfig" I keep seeing things
   like this in my build:

scripts/kconfig/conf --silentoldconfig Kconfig
include/config/auto.conf:986:warning: symbol value 'm' invalid for BT_SCO
include/config/auto.conf:3156:warning: symbol value 'm' invalid for BT_L2CAP

Reported-by: David S. Miller 
Signed-off-by: Gustavo F. Padovan 
Signed-off-by: John W. Linville

Bluetooth: Merge L2CAP and SCO modules into bluetooth.ko

2011-02-14T20:27:36+00:00

Actually doesn't make sense have these modules built separately.
The L2CAP layer is needed by almost all Bluetooth protocols and profiles.
There isn't any real use case without having L2CAP loaded.
SCO is only essential for Audio transfers, but it is so small that we can
have it loaded always in bluetooth.ko without problems.
If you really doesn't want it you can disable SCO in the kernel config.

Signed-off-by: Gustavo F. Padovan

Bluetooth: update Bluetooth daemon name in Kconfig help

2011-02-08T03:46:09+00:00

Change hcid to bluetoothd.

Signed-off-by: Gustavo F. Padovan

Bluetooth: Remove L2CAP Extended Features from Kconfig

2010-07-21T17:39:04+00:00

This reverts commit 84fb0a6334af0ccad3544f6972c055d90fbb9fbe which adds
the L2CAP Extended Features to the Kconfig, that is actually not needed.
One can use other mechanisms to enable L2CAP Extended Features.

Signed-off-by: Gustavo F. Padovan 
Signed-off-by: Marcel Holtmann