OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/drivers/entropy/Kconfig.mcux

24 lines
640 B
Plaintext
Raw Normal View History

drivers: Rename `random` to `entropy` This should clear up some of the confusion with random number generators and drivers that obtain entropy from the hardware. Also, many hardware number generators have limited bandwidth, so it's natural for their output to be only used for seeding a random number generator. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-10-14 07:30:55 +08:00
# Kconfig.mcux - mcux entropy generator driver configuration
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
#
# Copyright (c) 2016 ARM Ltd.
#
license: Replace Apache boilerplate with SPDX tag Replace the existing Apache 2.0 boilerplate header with an SPDX tag throughout the zephyr code tree. This patch was generated via a script run over the master branch. Also updated doc/porting/application.rst that had a dependency on line numbers in a literal include. Manually updated subsys/logging/sys_log.c that had a malformed header in the original file. Also cleanup several cases that already had a SPDX tag and we either got a duplicate or missed updating. Jira: ZEP-1457 Change-Id: I6131a1d4ee0e58f5b938300c2d2fc77d2e69572c Signed-off-by: David B. Kinder <david.b.kinder@intel.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-01-19 09:01:01 +08:00
# SPDX-License-Identifier: Apache-2.0
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
drivers: Rename `random` to `entropy` This should clear up some of the confusion with random number generators and drivers that obtain entropy from the hardware. Also, many hardware number generators have limited bandwidth, so it's natural for their output to be only used for seeding a random number generator. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-10-14 07:30:55 +08:00
menuconfig ENTROPY_MCUX_RNGA
random: mcux: rename random_mcux to random_mcux_rnga MCUX contains more than one type of random number generator, so refrect this in config and file names. Change-Id: Iba4482a1ae41f35d471686f8b159c113147c4df8 Signed-off-by: Bogdan Davidoaia <bogdan.davidoaia@linaro.org>
2017-02-27 22:45:08 +08:00
bool "MCUX RNGA driver"
drivers: Rename `random` to `entropy` This should clear up some of the confusion with random number generators and drivers that obtain entropy from the hardware. Also, many hardware number generators have limited bandwidth, so it's natural for their output to be only used for seeding a random number generator. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-10-14 07:30:55 +08:00
depends on ENTROPY_GENERATOR && HAS_MCUX_RNGA
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
default n
drivers: Rename `random` to `entropy` This should clear up some of the confusion with random number generators and drivers that obtain entropy from the hardware. Also, many hardware number generators have limited bandwidth, so it's natural for their output to be only used for seeding a random number generator. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-10-14 07:30:55 +08:00
select ENTROPY_HAS_DRIVER
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
help
This option enables the random number generator accelerator (RNGA)
random: Rename ksdk to mcux Renames the ksdk random generator shim driver to mcux. Change-Id: I8bc376937fed3024c809782139a0a72c7332f89a Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2017-01-03 04:24:58 +08:00
driver based on the MCUX RNGA driver.
random: add MCUX TRNG driver Provide a random driver wrapped around the MCUX TRNG driver. Change-Id: Icbd7ab587aa18ecbd7eae52290aaa5d8ee504cf2 Origin: Original Signed-off-by: Bogdan Davidoaia <bogdan.davidoaia@linaro.org>
2017-02-28 19:24:43 +08:00
drivers: Rename `random` to `entropy` This should clear up some of the confusion with random number generators and drivers that obtain entropy from the hardware. Also, many hardware number generators have limited bandwidth, so it's natural for their output to be only used for seeding a random number generator. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-10-14 07:30:55 +08:00
menuconfig ENTROPY_MCUX_TRNG
random: add MCUX TRNG driver Provide a random driver wrapped around the MCUX TRNG driver. Change-Id: Icbd7ab587aa18ecbd7eae52290aaa5d8ee504cf2 Origin: Original Signed-off-by: Bogdan Davidoaia <bogdan.davidoaia@linaro.org>
2017-02-28 19:24:43 +08:00
bool "MCUX TRNG driver"
drivers: Rename `random` to `entropy` This should clear up some of the confusion with random number generators and drivers that obtain entropy from the hardware. Also, many hardware number generators have limited bandwidth, so it's natural for their output to be only used for seeding a random number generator. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-10-14 07:30:55 +08:00
depends on ENTROPY_GENERATOR && HAS_MCUX_TRNG
random: add MCUX TRNG driver Provide a random driver wrapped around the MCUX TRNG driver. Change-Id: Icbd7ab587aa18ecbd7eae52290aaa5d8ee504cf2 Origin: Original Signed-off-by: Bogdan Davidoaia <bogdan.davidoaia@linaro.org>
2017-02-28 19:24:43 +08:00
default n
drivers: Rename `random` to `entropy` This should clear up some of the confusion with random number generators and drivers that obtain entropy from the hardware. Also, many hardware number generators have limited bandwidth, so it's natural for their output to be only used for seeding a random number generator. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-10-14 07:30:55 +08:00
select ENTROPY_HAS_DRIVER
random: add MCUX TRNG driver Provide a random driver wrapped around the MCUX TRNG driver. Change-Id: Icbd7ab587aa18ecbd7eae52290aaa5d8ee504cf2 Origin: Original Signed-off-by: Bogdan Davidoaia <bogdan.davidoaia@linaro.org>
2017-02-28 19:24:43 +08:00
help
This option enables the true random number generator (TRNG)
driver based on the MCUX TRNG driver.