OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/soc/arm/nordic_nrf/validate_base_addresses.c

138 lines
4.0 KiB
C
Raw Normal View History

soc: nordic_nrf: Add validation of base addresses defined in dts Add a set of build time assertions that checks if the peripheral base addresses defined in dts nodes match the values provided by nrfx/MDK. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-09-23 20:26:56 +08:00
/*
soc: nordic_nrf: validate base addresses with new DT API Use the new devicetree API in a file which cross-checks dt reg base addresses with values from the vendor HAL. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-03-25 10:32:31 +08:00
* Copyright (c) 2019, 2020 Nordic Semiconductor ASA
soc: nordic_nrf: Add validation of base addresses defined in dts Add a set of build time assertions that checks if the peripheral base addresses defined in dts nodes match the values provided by nrfx/MDK. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-09-23 20:26:56 +08:00
*
* SPDX-License-Identifier: Apache-2.0
*/
#include <kernel.h>
soc: nordic_nrf: validate base addresses with new DT API Use the new devicetree API in a file which cross-checks dt reg base addresses with values from the vendor HAL. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-03-25 10:32:31 +08:00
#include <soc.h>
#include <devicetree.h>
soc: nordic_nrf: Add validation of base addresses defined in dts Add a set of build time assertions that checks if the peripheral base addresses defined in dts nodes match the values provided by nrfx/MDK. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-09-23 20:26:56 +08:00
/*
soc: nordic_nrf: validate base addresses with new DT API Use the new devicetree API in a file which cross-checks dt reg base addresses with values from the vendor HAL. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-03-25 10:32:31 +08:00
* Account for MDK inconsistencies
modules: hal_nordic: Update nrfx to version 2.1.0 Update the hal_nordic module revision, to switch to nrfx 2.1.0. Because the list of peripherals for nRF5340 has changed as follows: - SPIM2 has been renamed to SPIM4 - SPIM2-3, SPIS2-3, TWIM2-3, TWIS2-3, and UARTE2-3 have been added a couple of related corrections needed to be applied in dts and Kconfig files, plus the spi_nrfx_spim driver has been extended with the support for SPIM4. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2020-01-24 23:22:50 +08:00
*/
soc: nordic_nrf: Add validation of base addresses defined in dts Add a set of build time assertions that checks if the peripheral base addresses defined in dts nodes match the values provided by nrfx/MDK. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-09-23 20:26:56 +08:00
soc: nordic_nrf: validate base addresses with new DT API Use the new devicetree API in a file which cross-checks dt reg base addresses with values from the vendor HAL. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-03-25 10:32:31 +08:00
#if !defined(NRF_I2S0) && defined(NRF_I2S)
#define NRF_I2S0 NRF_I2S
soc: nordic_nrf: Add validation of base addresses defined in dts Add a set of build time assertions that checks if the peripheral base addresses defined in dts nodes match the values provided by nrfx/MDK. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-09-23 20:26:56 +08:00
#endif
soc: nordic_nrf: validate base addresses with new DT API Use the new devicetree API in a file which cross-checks dt reg base addresses with values from the vendor HAL. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-03-25 10:32:31 +08:00
#if !defined(NRF_P0) && defined(NRF_GPIO)
#define NRF_P0 NRF_GPIO
soc: nordic_nrf: Add validation of base addresses defined in dts Add a set of build time assertions that checks if the peripheral base addresses defined in dts nodes match the values provided by nrfx/MDK. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-09-23 20:26:56 +08:00
#endif
soc: nordic_nrf: validate base addresses with new DT API Use the new devicetree API in a file which cross-checks dt reg base addresses with values from the vendor HAL. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-03-25 10:32:31 +08:00
#if !defined(NRF_PDM0) && defined(NRF_PDM)
#define NRF_PDM0 NRF_PDM
soc: nordic_nrf: Add validation of base addresses defined in dts Add a set of build time assertions that checks if the peripheral base addresses defined in dts nodes match the values provided by nrfx/MDK. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-09-23 20:26:56 +08:00
#endif
soc: nordic_nrf: validate base addresses with new DT API Use the new devicetree API in a file which cross-checks dt reg base addresses with values from the vendor HAL. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-03-25 10:32:31 +08:00
#if !defined(NRF_WDT0) && defined(NRF_WDT)
#define NRF_WDT0 NRF_WDT
soc: nordic_nrf: Update validation of base adresses with new entries Add checks for: - NRF_RNG - NRF_IPC - NRF_WDT0 - NRF_WDT1 Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-10-25 22:11:35 +08:00
#endif
soc: nordic_nrf: validate base addresses with new DT API Use the new devicetree API in a file which cross-checks dt reg base addresses with values from the vendor HAL. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-03-25 10:32:31 +08:00
/**
* Check that a devicetree node's "reg" base address matches the
* correct value from the MDK.
*
devicetree: remove DT_HAS_NODE_STATUS_OKAY Several reviewers agreed that DT_HAS_NODE_STATUS_OKAY(...) was an undesirable API for the following reasons: - it's inconsistent with the rest of the DT_NODE_HAS_FOO names - DT_NODE_HAS_FOO_BAR_BAZ(node) was agreed upon as a shorthand for macros which are equivalent to DT_NODE_HAS_FOO(node) && DT_NODE_HAS_BAR(node) && - DT_NODE_HAS_BAZ(node), and DT_HAS_NODE_STATUS_OKAY is an odd duck - DT_NODE_HAS_STATUS(..., okay) was viewed as more readable anyway - it is seen as a somewhat aesthetically challenged name Replace all users with DT_NODE_HAS_STATUS(..., okay), which is semantically equivalent. This is mostly done with sed, but a few remaining cases were done by hand, along with whitespace, docs, and comment changes. These special cases include the Nordic SOC static assert files. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-05-12 02:56:08 +08:00
* Node reg values are checked against MDK addresses regardless of
* their status.
soc: nordic_nrf: validate base addresses with new DT API Use the new devicetree API in a file which cross-checks dt reg base addresses with values from the vendor HAL. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-03-25 10:32:31 +08:00
*
devicetree: remove DT_HAS_NODE_STATUS_OKAY Several reviewers agreed that DT_HAS_NODE_STATUS_OKAY(...) was an undesirable API for the following reasons: - it's inconsistent with the rest of the DT_NODE_HAS_FOO names - DT_NODE_HAS_FOO_BAR_BAZ(node) was agreed upon as a shorthand for macros which are equivalent to DT_NODE_HAS_FOO(node) && DT_NODE_HAS_BAR(node) && - DT_NODE_HAS_BAZ(node), and DT_HAS_NODE_STATUS_OKAY is an odd duck - DT_NODE_HAS_STATUS(..., okay) was viewed as more readable anyway - it is seen as a somewhat aesthetically challenged name Replace all users with DT_NODE_HAS_STATUS(..., okay), which is semantically equivalent. This is mostly done with sed, but a few remaining cases were done by hand, along with whitespace, docs, and comment changes. These special cases include the Nordic SOC static assert files. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-05-12 02:56:08 +08:00
* Using a node label allows the same file to work with multiple SoCs
* and devicetree configurations.
soc: nordic_nrf: validate base addresses with new DT API Use the new devicetree API in a file which cross-checks dt reg base addresses with values from the vendor HAL. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-03-25 10:32:31 +08:00
*
* @param lbl lowercase-and-underscores devicetree node label to check
* @param mdk_addr expected address from the Nordic MDK.
*/
#define CHECK_DT_REG(lbl, mdk_addr) \
BUILD_ASSERT( \
devicetree: remove DT_HAS_NODE_STATUS_OKAY Several reviewers agreed that DT_HAS_NODE_STATUS_OKAY(...) was an undesirable API for the following reasons: - it's inconsistent with the rest of the DT_NODE_HAS_FOO names - DT_NODE_HAS_FOO_BAR_BAZ(node) was agreed upon as a shorthand for macros which are equivalent to DT_NODE_HAS_FOO(node) && DT_NODE_HAS_BAR(node) && - DT_NODE_HAS_BAZ(node), and DT_HAS_NODE_STATUS_OKAY is an odd duck - DT_NODE_HAS_STATUS(..., okay) was viewed as more readable anyway - it is seen as a somewhat aesthetically challenged name Replace all users with DT_NODE_HAS_STATUS(..., okay), which is semantically equivalent. This is mostly done with sed, but a few remaining cases were done by hand, along with whitespace, docs, and comment changes. These special cases include the Nordic SOC static assert files. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-05-12 02:56:08 +08:00
UTIL_OR(UTIL_NOT(DT_NODE_EXISTS(DT_NODELABEL(lbl))), \
zephyr: replace zephyr integer types with C99 types git grep -l 'u\(8\|16\|32\|64\)_t' | \ xargs sed -i "s/u\(8\|16\|32\|64\)_t/uint\1_t/g" git grep -l 's\(8\|16\|32\|64\)_t' | \ xargs sed -i "s/s\(8\|16\|32\|64\)_t/int\1_t/g" Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2020-05-28 00:26:57 +08:00
(DT_REG_ADDR(DT_NODELABEL(lbl)) == (uint32_t)(mdk_addr))))
soc: nordic_nrf: validate base addresses with new DT API Use the new devicetree API in a file which cross-checks dt reg base addresses with values from the vendor HAL. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-03-25 10:32:31 +08:00
/**
* If a node label "lbl" might have different addresses depending on
* its compatible "compat", you can use this macro to pick the right
* one.
*
* @param lbl lowercase-and-underscores devicetree node label to check
* @param compat lowercase-and-underscores compatible to check
* @param addr_if_match MDK address to return if "lbl" has compatible "compat"
* @param addr_if_no_match MDK address to return otherwise
*/
#define NODE_ADDRESS(lbl, compat, addr_if_match, addr_if_no_match) \
devicetree: DT_NODE_HAS_COMPAT_STATUS_OKAY -> DT_NODE_HAS_COMPAT_STATUS Swap this out and make the status a parameter. Leave a couple of cases of DT_NODE_HAS_COMPAT(). Signed-off-by: Kumar Gala <kumar.gala@linaro.org> Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-05-08 01:22:26 +08:00
COND_CODE_1(DT_NODE_HAS_COMPAT(DT_NODELABEL(lbl), compat), \
soc: nordic_nrf: validate base addresses with new DT API Use the new devicetree API in a file which cross-checks dt reg base addresses with values from the vendor HAL. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-03-25 10:32:31 +08:00
(addr_if_match), (addr_if_no_match))
#define CHECK_SPI_REG(lbl, num) \
CHECK_DT_REG(lbl, \
NODE_ADDRESS(lbl, nordic_nrf_spi, NRF_SPI##num, \
NODE_ADDRESS(lbl, nordic_nrf_spim, NRF_SPIM##num, \
NRF_SPIS##num)))
#define CHECK_I2C_REG(lbl, num) \
CHECK_DT_REG(lbl, \
NODE_ADDRESS(lbl, nordic_nrf_twi, NRF_TWI##num, \
NODE_ADDRESS(lbl, nordic_nrf_twim, NRF_TWIM##num, \
NRF_TWIS##num)))
#define CHECK_UART_REG(lbl, num) \
CHECK_DT_REG(lbl, \
NODE_ADDRESS(lbl, nordic_nrf_uart, NRF_UART##num, \
NRF_UARTE##num))
CHECK_DT_REG(adc, NODE_ADDRESS(adc, nordic_nrf_adc, NRF_ADC, NRF_SAADC));
CHECK_DT_REG(clock, NRF_CLOCK);
CHECK_DT_REG(cryptocell, NRF_CRYPTOCELL);
CHECK_DT_REG(dppic, NRF_DPPIC);
soc: nordic_nrf: Add validation of base addresses of ECB nodes from DT Add check that validates that the base addresses specified in DT nodes representing the ECB peripheral match the addresses of that peripheral defined in MDK. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2020-12-21 21:37:23 +08:00
CHECK_DT_REG(ecb, NRF_ECB);
soc: nordic_nrf: validate base addresses with new DT API Use the new devicetree API in a file which cross-checks dt reg base addresses with values from the vendor HAL. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-03-25 10:32:31 +08:00
CHECK_DT_REG(egu0, NRF_EGU0);
CHECK_DT_REG(egu1, NRF_EGU1);
CHECK_DT_REG(egu2, NRF_EGU2);
CHECK_DT_REG(egu3, NRF_EGU3);
CHECK_DT_REG(egu4, NRF_EGU4);
CHECK_DT_REG(egu5, NRF_EGU5);
CHECK_DT_REG(ficr, NRF_FICR);
CHECK_DT_REG(flash_controller, NRF_NVMC);
CHECK_DT_REG(gpio0, NRF_P0);
CHECK_DT_REG(gpio1, NRF_P1);
CHECK_DT_REG(gpiote, NRF_GPIOTE);
CHECK_DT_REG(i2s0, NRF_I2S0);
CHECK_DT_REG(ipc, NRF_IPC);
CHECK_DT_REG(kmu, NRF_KMU);
CHECK_DT_REG(pdm0, NRF_PDM0);
CHECK_DT_REG(power, NRF_POWER);
CHECK_DT_REG(pwm0, NRF_PWM0);
CHECK_DT_REG(pwm1, NRF_PWM1);
CHECK_DT_REG(pwm2, NRF_PWM2);
CHECK_DT_REG(pwm3, NRF_PWM3);
CHECK_DT_REG(qdec, NRF_QDEC);
CHECK_DT_REG(regulators, NRF_REGULATORS);
CHECK_DT_REG(rng, NRF_RNG);
CHECK_DT_REG(rtc0, NRF_RTC0);
CHECK_DT_REG(rtc1, NRF_RTC1);
CHECK_DT_REG(rtc2, NRF_RTC2);
CHECK_SPI_REG(spi0, 0);
CHECK_SPI_REG(spi1, 1);
CHECK_SPI_REG(spi2, 2);
CHECK_DT_REG(spi3, NRF_SPIM3);
CHECK_DT_REG(spi4, NRF_SPIM4);
CHECK_DT_REG(spu, NRF_SPU);
CHECK_DT_REG(temp, NRF_TEMP);
CHECK_DT_REG(timer0, NRF_TIMER0);
CHECK_DT_REG(timer1, NRF_TIMER1);
CHECK_DT_REG(timer2, NRF_TIMER2);
CHECK_DT_REG(timer3, NRF_TIMER3);
CHECK_DT_REG(timer4, NRF_TIMER4);
CHECK_I2C_REG(i2c0, 0);
CHECK_I2C_REG(i2c1, 1);
CHECK_DT_REG(i2c2, NRF_TWIM2);
CHECK_DT_REG(i2c3, NRF_TWIM3);
soc: nordic_nrf: add NRF_RADIO base address check Update validate_base_addresses.c for the RADIO peripheral. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2021-07-16 07:59:31 +08:00
CHECK_DT_REG(radio, NRF_RADIO);
soc: nordic_nrf: validate base addresses with new DT API Use the new devicetree API in a file which cross-checks dt reg base addresses with values from the vendor HAL. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-03-25 10:32:31 +08:00
CHECK_UART_REG(uart0, 0);
CHECK_DT_REG(uart1, NRF_UARTE1);
CHECK_DT_REG(uart2, NRF_UARTE2);
CHECK_DT_REG(uart3, NRF_UARTE3);
CHECK_DT_REG(uicr, NRF_UICR);
CHECK_DT_REG(usbd, NRF_USBD);
CHECK_DT_REG(vmc, NRF_VMC);
dts: nordic: introduce wdt0 / wdt1 distinction Add wdt0 node labels for all watchdogs. Keep the existing wdt node labels in place for backwards compatibility. Add a wdt1 node to the nRF5340 application core .dtsi, but leave it disabled. Leave the wdt node's label set to "WDT" on this core for backwards compatibility also, in case any users are getting it with a string literal instead of asking the devicetree. This can be changed later after this round of watchdog changes has been shaken out and tested more. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-04-17 08:08:50 +08:00
CHECK_DT_REG(wdt, NRF_WDT0); /* this should be the same node as wdt0 */
CHECK_DT_REG(wdt0, NRF_WDT0);
CHECK_DT_REG(wdt1, NRF_WDT1);