RIOT-OS/RIOT
RIOT-OS/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
Code Releases Activity
5d76abffa1
RIOT/drivers/atwinc15x0/Makefile.dep

27 lines
859 B
Makefile
Raw Normal View History

drivers: configure per driver dependency resolution
2020-06-26 21:55:37 +02:00
USEMODULE += netdev_eth
drivers/atwinc15x0: mirgate to ztimer
2021-12-11 09:24:54 +01:00
USEMODULE += ztimer_msec
sys/net/gnrc/netif: allow checking if a netdev is legacy or new API A if `netdev_driver_t::confirm_send()` is provided, it provides the new netdev API. However, detecting the API at runtime and handling both API styles comes at a cost. This can be optimized in case only new or only old style netdevs are in use. To do so, this adds the pseudo modules `netdev_legacy_api` and `netdev_new_api`. As right now no netdev actually implements the new API, all netdevs pull in `netdev_legacy_api`. If `netdev_legacy_api` is in used but `netdev_new_api` is not, we can safely assume at compile time that only legacy netdevs are in use. Similar, if only `netdev_new_api` is used, only support for the new API is needed. Only when both are in use, run time checks are needed. This provides two helper function to check for a netif if the corresponding netdev implements the old or the new API. (With one being the inverse of the other.) They are suitable for constant folding when only new or only legacy devices are in use. Consequently, dead branches should be eliminated by the optimizer.
2022-08-09 14:58:36 +02:00
USEMODULE += netdev_legacy_api
drivers/atwinc15x0: support network scanning and dynamic connection There are new pseudomodules for this driver: - atwinc15x0_static_connect: Should behave as before, by trying to connect to an AP by specified WIFI_SSIS and WIFI_PASS - atwinc15x0_dynamic_connect: takes connection request via NETOPT_CONNECT and provides the connection result via callback - atwinc15x0_dynamic_scan: takes network scan requests via NETOPT_SCAN and provides the scan result as a sorted list via callback
2023-03-14 10:42:08 +01:00
ifeq (,$(filter atwinc15x0_dynamic_%,$(USEMODULE)))
# use static connect by default when no dynamic module is loaded
USEMODULE += atwinc15x0_static_connect
endif
ifneq (,$(filter atwinc15x0_dynamic_scan,$(USEMODULE)))
USEMODULE += wifi_scan_list
endif
ifneq (,$(filter atwinc15x0_static_connect,$(USEMODULE)))
USEMODULE += ztimer
endif
drivers: configure per driver dependency resolution
2020-06-26 21:55:37 +02:00
USEPKG += driver_atwinc15x0
FEATURES_REQUIRED += periph_gpio
FEATURES_REQUIRED += periph_gpio_irq
FEATURES_REQUIRED += periph_spi
drivers/atwinc15x0: blacklist esp8266
2022-06-19 16:53:34 +02:00
drivers/atwinc15x0: blacklist esp32 architecure esp32 vendor code and atwinc15x0 both define conflicting spi_flash_{read, write} functions. esp32 already have build-in WiFi, so it's unlikely to ever use this driver - just blacklist the architecture.
2022-06-23 23:24:15 +02:00
# esp8266 and esp32 vendor code and atwinc15x0 both define conflicting
drivers/atwinc15x0: blacklist esp8266
2022-06-19 16:53:34 +02:00
# spi_flash_{read, write} functions.
drivers/atwinc15x0: blacklist esp32 architecure esp32 vendor code and atwinc15x0 both define conflicting spi_flash_{read, write} functions. esp32 already have build-in WiFi, so it's unlikely to ever use this driver - just blacklist the architecture.
2022-06-23 23:24:15 +02:00
# esp8266 and esp32 already have build-in WiFi, so it's unlikely to ever
drivers/atwinc15x0: blacklist esp8266
2022-06-19 16:53:34 +02:00
# use this driver - just blacklist the architecture.
FEATURES_BLACKLIST += arch_esp8266
drivers/atwinc15x0: blacklist esp32 architecure esp32 vendor code and atwinc15x0 both define conflicting spi_flash_{read, write} functions. esp32 already have build-in WiFi, so it's unlikely to ever use this driver - just blacklist the architecture.
2022-06-23 23:24:15 +02:00
FEATURES_BLACKLIST += arch_esp32
Copy Permalink