zephyr/samples/bluetooth/peripheral_csc/prj.conf

CONFIG_RANDOM_GENERATOR=y
CONFIG_TEST_RANDOM_GENERATOR=y
CONFIG_BLUETOOTH=y
CONFIG_BLUETOOTH_PERIPHERAL=y
CONFIG_BLUETOOTH_DEVICE_NAME="CSC peripheral"
random: Restructure RANDOM Kconfig Restructure the RANDOM Kconfig to match the structure used in other drivers with a single top level menu. Move the true random number generators to appear first in the menu, with pseudo generators at the bottom. Do not present pseudo generators if a true random generator is presented. This change implies that tests, samples and applications that require the random driver interface must now select CONFIG_RANDOM_GENERATOR. In order for tests and samples to build (and run) on platforms that have no random driver it remains necessary to select the CONFIG_TEST_RANDOM_GENERATOR. Note that CONFIG_TEST_RANDOM_GENERATOR retains its original purpose of enabling a random driver that delivers non random numbers for the purpose of testing only. Change-Id: I2e28e44b4adf800e64a885aefe36a52da8aa455a Signed-off-by: Marcus Shawcroft <marcus.shawcroft@arm.com> 2016-11-29 04:39:43 +08:00			`CONFIG_RANDOM_GENERATOR=y`
Bluetooth: Add Cycling Speed and Cadence sample application This adds sample application that implements Cycling Speed and Cadence profile. Change-Id: I0fd94582887ca3f5fdc363f35e5a3304c5f64cd9 Signed-off-by: Mariusz Skamra <mariusz.skamra@tieto.com> 2016-02-10 20:38:15 +08:00			`CONFIG_TEST_RANDOM_GENERATOR=y`
			`CONFIG_BLUETOOTH=y`
			`CONFIG_BLUETOOTH_PERIPHERAL=y`
Bluetooth: samples: Use Kconfig DEVICE_NAME variable when possible Instead of using a hard-coded string, make the sample use the Kconfig variable for the device name. Change-Id: Ib09f594e1cba221f9064318572bd90d38bd2733a Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> 2017-01-27 21:41:59 +08:00			`CONFIG_BLUETOOTH_DEVICE_NAME="CSC peripheral"`