2022-01-26 16:11:55 +01:00
|
|
|
BOARD ?= nucleo-f767zi
|
|
|
|
|
|
|
|
|
|
# Custom per-board pin configuration (e.g. for setting PORT_IN, PIN_IN_0, ...)
|
|
|
|
|
# can be provided in a Makefile.$(BOARD) file:
|
|
|
|
|
-include Makefile.$(BOARD)
|
|
|
|
|
|
|
|
|
|
# Choose two output pins that do not conflict with stdio and are not connected
|
|
|
|
|
# to external devices such as sensors, network devices, etc.
|
|
|
|
|
#
|
|
|
|
|
# Beware: If other pins on the output port are configured as output GPIOs, they
|
|
|
|
|
# might be written to during this test.
|
drivers/periph_gpio_ll: change API to access GPIO ports
The API was based on the assumption that GPIO ports are mapped in memory
sanely, so that a `GPIO_PORT(num)` macro would work allow for constant
folding when `num` is known and still be efficient when it is not.
Some MCUs, however, will need a look up tables to efficiently translate
GPIO port numbers to the port's base address. This will prevent the use
of such a `GPIO_PORT(num)` macro in constant initializers.
As a result, we rather provide `GPIO_PORT_0`, `GPIO_PORT_1`, etc. macros
for each GPIO port present (regardless of MCU naming scheme), as well as
`GPIO_PORT_A`, `GPIO_PORT_B`, etc. macros if (and only if) the MCU port
naming scheme uses letters rather than numbers.
These can be defined as macros to the peripheral base address even when
those are randomly mapped into the address space. In addition, a C
function `gpio_port()` replaces the role of the `GPIO_PORT()` and
`gpio_port_num()` the `GPIO_PORT_NUM()` macro. Those functions will
still be implemented as efficient as possible and will allow constant
folding where it was formerly possible. Hence, there is no downside for
MCUs with sane peripheral memory mapping, but it is highly beneficial
for the crazy ones.
There are also two benefits for the non-crazy MCUs:
1. We can now test for valid port numbers with `#ifdef GPIO_PORT_<NUM>`
- This directly benefits the test in `tests/periph/gpio_ll`, which
can now provide a valid GPIO port for each and every board
- Writing to invalid memory mapped I/O addresses was treated as
triggering undefined behavior by the compiler and used as a
optimization opportunity
2. We can now detect at compile time if the naming scheme of the MCU
uses letters or numbers, and produce more user friendly output.
- This is directly applied in the test app
2024-04-29 13:32:24 +02:00
|
|
|
#PORT_OUT := 0
|
2022-01-26 16:11:55 +01:00
|
|
|
PIN_OUT_0 ?= 0
|
|
|
|
|
PIN_OUT_1 ?= 1
|
|
|
|
|
|
2023-05-10 09:47:10 +02:00
|
|
|
include ../Makefile.bench_common
|
2022-01-26 16:11:55 +01:00
|
|
|
|
|
|
|
|
FEATURES_REQUIRED += periph_gpio_ll
|
|
|
|
|
FEATURES_REQUIRED += periph_gpio
|
|
|
|
|
FEATURES_OPTIONAL += periph_gpio_ll_irq
|
|
|
|
|
FEATURES_OPTIONAL += periph_gpio_ll_irq_level_triggered_high
|
|
|
|
|
FEATURES_OPTIONAL += periph_gpio_ll_irq_level_triggered_low
|
|
|
|
|
|
|
|
|
|
USEMODULE += ztimer_usec
|
|
|
|
|
|
|
|
|
|
include $(RIOTBASE)/Makefile.include
|
|
|
|
|
|
|
|
|
|
# Configure if compensation of loop overhead in the estimation of the
|
|
|
|
|
# toggling speed should be performed. Default: Do so, except for Cortex-M7.
|
|
|
|
|
# For the Cortex-M7 the loop instructions are emitted together with the GPIO
|
|
|
|
|
# writes due to the dual issue feature. Hence, there is no loop overhead for
|
|
|
|
|
# Cortex-M7 to compensate for.
|
|
|
|
|
ifeq (cortex-m7,$(CPU_CORE))
|
|
|
|
|
COMPENSATE_OVERHEAD ?= 0
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
COMPENSATE_OVERHEAD ?= 1
|
|
|
|
|
|
drivers/periph_gpio_ll: change API to access GPIO ports
The API was based on the assumption that GPIO ports are mapped in memory
sanely, so that a `GPIO_PORT(num)` macro would work allow for constant
folding when `num` is known and still be efficient when it is not.
Some MCUs, however, will need a look up tables to efficiently translate
GPIO port numbers to the port's base address. This will prevent the use
of such a `GPIO_PORT(num)` macro in constant initializers.
As a result, we rather provide `GPIO_PORT_0`, `GPIO_PORT_1`, etc. macros
for each GPIO port present (regardless of MCU naming scheme), as well as
`GPIO_PORT_A`, `GPIO_PORT_B`, etc. macros if (and only if) the MCU port
naming scheme uses letters rather than numbers.
These can be defined as macros to the peripheral base address even when
those are randomly mapped into the address space. In addition, a C
function `gpio_port()` replaces the role of the `GPIO_PORT()` and
`gpio_port_num()` the `GPIO_PORT_NUM()` macro. Those functions will
still be implemented as efficient as possible and will allow constant
folding where it was formerly possible. Hence, there is no downside for
MCUs with sane peripheral memory mapping, but it is highly beneficial
for the crazy ones.
There are also two benefits for the non-crazy MCUs:
1. We can now test for valid port numbers with `#ifdef GPIO_PORT_<NUM>`
- This directly benefits the test in `tests/periph/gpio_ll`, which
can now provide a valid GPIO port for each and every board
- Writing to invalid memory mapped I/O addresses was treated as
triggering undefined behavior by the compiler and used as a
optimization opportunity
2. We can now detect at compile time if the naming scheme of the MCU
uses letters or numbers, and produce more user friendly output.
- This is directly applied in the test app
2024-04-29 13:32:24 +02:00
|
|
|
ifneq (,$(PORT_OUT))
|
|
|
|
|
CFLAGS += -DPORT_OUT=GPIO_PORT_$(PORT_OUT)
|
|
|
|
|
CFLAGS += -DPORT_OUT_NUM=$(PORT_OUT)
|
|
|
|
|
endif
|
2022-01-26 16:11:55 +01:00
|
|
|
CFLAGS += -DPIN_OUT_0=$(PIN_OUT_0)
|
|
|
|
|
CFLAGS += -DPIN_OUT_1=$(PIN_OUT_1)
|
|
|
|
|
CFLAGS += -DCOMPENSATE_OVERHEAD=$(COMPENSATE_OVERHEAD)
|
