XTIMER_BACKOFF and XTIMER_ISR_BACKOFF were defined in periph_conf.h
since 2016 for the legacy xtimer module, which required high backoff
values (200) on native to prevent timer underflow issues.
However, since the migration to ztimer, all code now uses
MODULE_ZTIMER_XTIMER_COMPAT which includes ztimer/xtimer_compat.h
before periph_conf.h. This means xtimer_compat.h always defines
XTIMER_BACKOFF=1 first, and the periph_conf.h definitions are never
used.
Remove these unused definitions as they serve no purpose with the
current ztimer-based implementation.
Signed-off-by: Gilles DOFFE <g.doffe@gmail.com>
When not using the Rust version of Git-Cache, the build
system clones the full NRFX repository which led to errors during
the build process due to duplicated headers and headers not
found where they were expected.
The STM32F3 requires a dedicated digital signal to emulate a disconnect
event by pulling D+ down via a 1.5 kOhm resistor. Some boards, such as
the OLIMEXINO-STM32F3, do not directly connect a GPIO but place a
transistor in between. Depending on the exact implementation, the logic
level may end up being inverted compared to directly connecting a
GPIO.
This adds a flag member to the `stm32_usbdev_fs_config_t` and a new flag
to indicate inverted logic. In addition the members in the struct are
sorted by alignment, as this is a foolproof algorithm to prevent wasting
memory on unneeded padding.
Finally, the USB driver is adapted to honor the flag.
Co-authored-by: crasbe <crasbe@gmail.com>
The kinetis bme currently doesn't work properly. Temporarily disable the
use of the bme so that the default `sys/bit.h` implementation is used
instead.
- type in comment
- no space after `switch`
- overlong line
- `else` when the `if`-branch ends with a `return`
statement anyway
- drop of unused `#include`
- drop of unused function
- `int8_t` for RSSI in dBm when the API expects
`int16_t`
- This might actually fix an issue if the `int8_t` range could
overflow
The RMT driver module `esp_idf_rmt` uses GDMA on ESP32-S3, which in turn requires the activation and deactivation of flash encryption. Therefore, when the RMT driver module `esp_idf_rmt` is used, the function `gdma_disconnect` is used, which in turn requires the function `esp_flash_encryption_enabled`. However, if the NVS flash module `esp_idf_nvs_flash` is also used for some reason, e.g. because WiFi or BLE is used, the function `esp_flash_encryption_enabled` is already compiled in the module `esp_idf_nvs_flash` and must not be compiled again in the module `esp_idf_rmt`.
