Names of some testcases are duplicated in another files.
This change rename duplicated testcases.
Signed-off-by: Katarzyna Giadla <katarzyna.giadla@nordicsemi.no>
So far LOG_DBG() was used inside debug hook for mbedTLS library. This meant
that it was hard to distinct log messages by simply looking at the log
level number, even though Zephyr logging subsystem supports colorful logs
depending on log level.
Choose an appropriate Zephyr LOG_*() macro based on log level coming from
mbedTLS library. Remove log level number from formatted log messages, as it
is now redundant.
One controversial thing about this change is that mbedTLS' "2 State change"
log level is mapped to Zephyr's "warning" log level. Those are not really
warnings in real life, but rather informational messages. However, using
"warning" log level for those allows to clearly distinguish between "2
State change" and "3 Informational" debug messages from mbedTLS.
Additionally, mbedTLS debug message implementation does not seem to be safe
to use in production, so keeping in mind MBEDTLS_DEBUG will be enabled just
during debugging phase, printing "2 State change" logs as warnings should
not be a big deal.
Set default MBEDTLS_DEBUG_LEVEL value depending on selected Zephyr logging
module level, so that only single option needs to be configured in
application project.
Remove prompt for MBEDTLS_DEBUG_LEVEL, so that interactively (e.g. via
menuconfig) adjusting MBEDTLS_LOG_LEVEL will always result in automatically
updating MBEDTLS_DEBUG_LEVEL option. This is to prevent so called "stuck
symbol syndrome".
Signed-off-by: Marcin Niestroj <m.niestroj@emb.dev>
mbedTLS library threshold initialization was done in native TLS socket
implementation (which tends to use mbedTLS now) and inside mbedTLS
benchmark test. Move that to mbedTLS module initialization, as this is a
global setting.
Update description of CONFIG_MBEDTLS_DEBUG_LEVEL to clarify when
mbedtls_debug_set_threshold() is called.
Signed-off-by: Marcin Niestroj <m.niestroj@emb.dev>
The SBS Gauge driver is tested on a nucleo_f070rb board. This is an ARM
board so we should also verify on some Qemu emulated ARM platform.
Enable SBS Gauge driver test on an ARM platform, arbitrarily chosen as
qemu_cortex_a9.
TEST=twister -T tests/drivers/sensor/sbs_gauge
Signed-off-by: Aaron Massey <aaronmassey@google.com>
The SBS Gauge drivers tests only executed directly on hardware before. In
addition, the tests were flawed as they were only testing that behavior was
failing.
Enable the SBS Gauge emulator and fix driver tests so they execute
correctly.
TEST=twister -T tests/drivers/sensor/sbs_gauge
Signed-off-by: Aaron Massey <aaronmassey@google.com>
qemu_riscv32.overlay adds a device node for the ite,it8xxx2-bbram
which doesn't make any sense since for qemu_riscv32. Just remove
the file.
Signed-off-by: Kumar Gala <galak@kernel.org>
Now that bbram drivers are enabled based on devicetree we can
remove any cases of them getting enabled by *.conf files.
Signed-off-by: Kumar Gala <galak@kernel.org>
Partially revert commit 0028e9733295316d152eba07bf56677d83f4b1b5.
Timeout for tests/posix/common must be still increased for slow
platforms (previously was 120 sec).
Signed-off-by: Manuel Arguelles <manuel.arguelles@nxp.com>
* Reworked the stm32 SDRAM test to be more generic
* Added SRAM entries
* Moved to new ztest API
Signed-off-by: Pieter De Gendt <pieter.degendt@basalte.be>
The LE Audio related profiles define specific security requirements that
client have to met to gain access to related characteristics. This
introduces internal wrapper API for GATT characteristics and CCC
descriptors to ensure the security.
Signed-off-by: Mariusz Skamra <mariusz.skamra@codecoup.pl>
After moving the mbox_api test to new ztest API, one test failed
due to stack overflow on qemu_x86_lakemont. Add a little 64 extra
stack size for adapting it.
Signed-off-by: Enjia Mai <enjia.mai@intel.com>
Remove extra_args that set specific driver Kconfig symbols. This
will happen by default now since the drivers will be enabled if
they exist and are enabled in the devicetree.
Signed-off-by: Kumar Gala <galak@kernel.org>
Now that ethernet drivers are enabled based on devicetree we can
remove any cases of them getting enabled by proj.conf files.
Signed-off-by: Kumar Gala <galak@kernel.org>
Setting the new LLCP as default exposed errors in CI tests, which
are fixed here
Note that advanced scheduling needs to be disabled. Work is in
progress for implementing this for the new LLCP
Signed-off-by: Andries Kruithof <andries.kruithof@nordicsemi.no>
Because 1-wire drivers no longer use depends on serial/i2c, but select
the Kconfig for the bus they depend on, several overlays can be removed.
Signed-off-by: Thomas Stranger <thomas.stranger@outlook.com>
Bump CONFIG_MAX_THREAD_BYTES to 4 to get builds to pass. Since
we now enable I2C/SPI based if the device needs that bus, we end
up having more thread for all the drivers that get built in.
Since this a build only test there isn't any real issue with doing
this.
Signed-off-by: Kumar Gala <galak@kernel.org>
Remove extra_args that set specific driver Kconfig symbols. This
will happen by default now since the drivers will be enabled if
they exist and are enabled in the devicetree.
Signed-off-by: Kumar Gala <galak@kernel.org>
Merge I2C, SPI, and emul adc build tests and cleanup some
unneeded extra_args that enabled drivers. That will get
done via Kconfig defaults & devicetree now.
Signed-off-by: Kumar Gala <galak@kernel.org>
