Skip to content
Snippets Groups Projects
Unverified Commit 8d1a0ae0 authored by Alexandre Abadie's avatar Alexandre Abadie
Browse files

boards: revert forced use of periph_dma with STM32

The periph_dma is not pulled in automatically for all applications.
Applications willing to use the configured peripherals with periph_dma
for a given board will have to include the feature explictly in their
Makefile.

It was causing unrelated issues as threads got de-scheduled while
calling printf and this was not handled properly in tests at that
moment.
parent fc1badde
No related branches found
No related tags found
No related merge requests found
FEATURES_REQUIRED += periph_dma
ifneq (,$(filter netdev_default,$(USEMODULE)))
USEMODULE += sx1276
endif
......
FEATURES_REQUIRED += periph_dma
ifneq (,$(filter saul_default,$(USEMODULE)))
USEMODULE += saul_gpio
USEMODULE += hts221
......
include $(RIOTBOARD)/common/iotlab/Makefile.dep
FEATURES_REQUIRED += periph_dma
ifneq (,$(filter saul_default,$(USEMODULE)))
USEMODULE += isl29020
USEMODULE += lps331ap
......
FEATURES_REQUIRED += periph_dma
include $(RIOTBOARD)/common/nucleo/Makefile.dep
FEATURES_REQUIRED += periph_dma
include $(RIOTBOARD)/common/nucleo/Makefile.dep
FEATURES_REQUIRED += periph_dma
include $(RIOTBOARD)/common/nucleo/Makefile.dep
FEATURES_REQUIRED += periph_dma
include $(RIOTBOARD)/common/nucleo/Makefile.dep
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment