summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSeung-Woo Kim <sw0312.kim@samsung.com>2019-12-27 09:44:42 +0900
committerSeung-Woo Kim <sw0312.kim@samsung.com>2019-12-27 09:46:54 +0900
commitcca739e063d89ffefb0f385215c5929cfe4406e2 (patch)
tree8dbf4eded042a5c37bb9add66054880eef0e6d2a
parent05eb166e5bee540e420d15e9b379b8417f98727f (diff)
downloadtizen-kernel-configs-cca739e063d89ffefb0f385215c5929cfe4406e2.tar.gz
tizen-kernel-configs-cca739e063d89ffefb0f385215c5929cfe4406e2.tar.bz2
tizen-kernel-configs-cca739e063d89ffefb0f385215c5929cfe4406e2.zip
Bluetooth: Add CRYPTO_CCM for meshctl of BlueZ
To use meshctl of BlueZ, CRYPTO_CCM is required but it was missed even though it is already listed in security crypto options. Add CRYPTO_CCM option to BLE MESH part. Change-Id: I276360fa94fd74e6f6c171a5a06b4b0a00a60f4d Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
-rw-r--r--tizen/tizen_defconfig1
1 files changed, 1 insertions, 0 deletions
diff --git a/tizen/tizen_defconfig b/tizen/tizen_defconfig
index 0d7051a..2cb132c 100644
--- a/tizen/tizen_defconfig
+++ b/tizen/tizen_defconfig
@@ -549,6 +549,7 @@ CONFIG_BT_HCIBTUSB=y
# Tizen uses BLE Mesh with BlueZ and it requires CRYPTO_USER_API
# Ref. https://www.spinics.net/lists/linux-bluetooth/msg72012.html
# (Recommendation)
+CONFIG_CRYPTO_CCM=y
CONFIG_CRYPTO_CMAC=y
CONFIG_CRYPTO_USER_API=y
CONFIG_CRYPTO_USER_API_HASH=y