zephyr/tests/drivers/gpio/gpio_basic_api/prj.conf

CONFIG_GPIO=y
CONFIG_ZTEST=y
CONFIG_ENTROPY_GENERATOR=y
CONFIG_TEST_RANDOM_GENERATOR=y
#CONFIG_TEST_USERSPACE=y
tests: add gpio driver test case the commit include 5 ztest cases, cover the basic gpio APIs including callback relevant and pin read/write functions. It proves workable on intel quark c1000 and arduino 101 platform Change-Id: Iab30aa841cfa440c1f773b5a8c5ce0d68346c353 Signed-off-by: jing wang <jing.j.wang@intel.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2016-12-08 14:47:29 +08:00			`CONFIG_GPIO=y`
			`CONFIG_ZTEST=y`
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			`CONFIG_ENTROPY_GENERATOR=y`
tests/gpio: don't call risk function According to Coverity, rand() is a risk function. So we use another method to generate random value. Coverity-CID: 160070 Change-Id: Icb7e06cd43cb8bade6596cc37e9d04bfc59e1de7 Signed-off-by: Qiu Peiyang <peiyangx.qiu@intel.com> 2017-01-23 13:38:20 +08:00			`CONFIG_TEST_RANDOM_GENERATOR=y`
test/drivers/gpio: add tests for new API Test that the new port API functions all behave as expected, including physical vs logical level for input and output as well as masked and set-based output operations. Also tests the new pin API functions. For running on real hardware this test now uses a local test-specific devicetree binding. For build-only tests any platform with a GPIO alias should be tested. The new code increases flash requirements so add a filter to exclude platforms that won't link. Signed-off-by: Peter Bigot <peter.bigot@nordicsemi.no> 2019-11-14 01:01:37 +08:00			`#CONFIG_TEST_USERSPACE=y`