zephyr/tests/drivers/adc/adc_api/prj.conf

CONFIG_ZTEST=y

CONFIG_ADC=y
CONFIG_ADC_ASYNC=y
CONFIG_ADC_0=y
CONFIG_LOG=y
CONFIG_ADC_LOG_LEVEL_INF=y
CONFIG_LOG_IMMEDIATE=y
CONFIG_HEAP_MEM_POOL_SIZE=1024
CONFIG_TEST_USERSPACE=y
drivers: adc: Introduce reworked API This commit replaces the API for ADC drivers with a reworked one. As requested in the issue #3980, the adc_enable/adc_disable functions are removed. Additionaly, some new features are introduced, like: - asynchronous calls - configuration of channels - multi-channel sampling Common parts of code that are supposed to appear in each implementation of the driver (like locking, synchronization, triggering of consecutive samplings) are provided in the "adc_context.h" file to keep consistency with the SPI driver. Syscalls are no longer present in the API because the functions starting read requests cannot use them, since they can be provided with a callback that is executed in the ISR context, and there is no point in supporting syscalls only for the channels configuration. "adc_api" test is updated and extended with additional test cases, with intention to show how the API is supposed to be used. "adc_simple" test is removed as it does not seem to add much value. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no> 2018-05-21 21:00:28 +08:00			`CONFIG_ZTEST=y`

			`CONFIG_ADC=y`
			`CONFIG_ADC_ASYNC=y`
			`CONFIG_ADC_0=y`
drivers: adc: move to new logger Move to new logger subsystem. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2018-09-18 01:00:47 +08:00			`CONFIG_LOG=y`
			`CONFIG_ADC_LOG_LEVEL_INF=y`
tests: adc: reduce footprint by tweaking logging Using CONFIG_LOG_IMMEDIATE gives us some flash back. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2019-02-13 04:54:40 +08:00			`CONFIG_LOG_IMMEDIATE=y`
tests: adc_api: run adc_read_async() from user We define a system heap and assign our resource pool from it as k_poll() requires an implicit allocation. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com> 2019-04-02 03:16:44 +08:00			`CONFIG_HEAP_MEM_POOL_SIZE=1024`
tests: CONFIG_TEST_USERSPACE now off by default Unlike CONFIG_HW_STACK_PROTECTION, which greatly helps expose stack overflows in test code, activating userspace without putting threads in user mode is of very limited value. Now CONFIG_TEST_USERSPACE is off by default. Any test which puts threads in user mode will need to set CONFIG_TEST_USERSPACE. This should greatly increase sanitycheck build times as there is non-trivial build time overhead to enabling this feature. This also allows some tests which failed the build on RAM-constrained platforms to compile properly. tests/drivers/build_all is a special case; it doesn't put threads in user mode, but we want to ensure all the syscall handlers compile properly. Fixes: #15103 (and probably others) Signed-off-by: Andrew Boie <andrew.p.boie@intel.com> 2019-04-06 06:39:50 +08:00			`CONFIG_TEST_USERSPACE=y`