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
d8cf5a0c66
RIOT/cpu/fe310/Kconfig

58 lines
1.4 KiB
Plaintext
Raw Normal View History

cpu/fe310: add Kconfig configuration
2020-06-23 21:39:14 +02:00
# Copyright (c) 2020 Inria
#
# This file is subject to the terms and conditions of the GNU Lesser
# General Public License v2.1. See the file LICENSE in the top level
# directory for more details.
#
config CPU_FAM_FE310
bool
cpu/fe310: add CPU_CORE information
2021-09-22 15:51:54 +02:00
select CPU_CORE_RV32IMAC
cpu/fe310: add Kconfig configuration
2020-06-23 21:39:14 +02:00
select HAS_CPU_FE310
select HAS_PERIPH_CPUID
select HAS_PERIPH_GPIO
select HAS_PERIPH_GPIO_IRQ
select HAS_PERIPH_PM
cpu/riscv_common: only select PLIC for fe310 Not every RISC-V implements that interrupt controller, gd32v uses CLIC instead.
2021-08-25 10:49:47 +02:00
select HAS_PERIPH_PLIC
cpu: add periph_rtt_overflow feature The RTT overflow callback is not available on all RTT implementations. This means it is either a no-op or `rtt_set_overflow_cb()` is a no-op or it will overwrite the alarm set with `rtt_set_alarm()`. This adds a feature to indicate that proper overflow reporting is available.
2021-01-13 20:48:29 +01:00
select HAS_PERIPH_RTT_OVERFLOW
drivers/periph/rtt: add periph_rtt_set_counter feature Some periph_rtt implementations do not provide `rtt_set_counter()`. This adds `periph_rtt_set_counter` as feature to allow testing for its availability. The feature is provided at CPU level if periph_rtt is provided by the board for all CPUs implementing `rtt_set_counter()`.
2021-03-04 20:04:11 +01:00
select HAS_PERIPH_RTT_SET_COUNTER
cpu/fe310: add Kconfig configuration
2020-06-23 21:39:14 +02:00
select HAS_PERIPH_WDT
cpu/fe310: model Kconfig
2021-09-28 16:18:15 +02:00
select MODULE_PERIPH_PLIC if TEST_KCONFIG
select MODULE_PERIPH_CORETIMER if MODULE_PERIPH_TIMER && HAS_PERIPH_CORETIMER
select MODULE_PERIPH_RTT if MODULE_PERIPH_RTC && HAS_PERIPH_RTT
cpu: do not auto-select ztimer_periph_rtt for sam0, fe310 The sam0 rtt busy loops for 180us every time an alarm is set or the counter is read, this propagates and leads to timing errors on ztimer_msec that are higher than > +-1msec. The same goes for fe310.
2021-12-14 18:43:53 +01:00
select MODULE_ZTIMER_NO_PERIPH_RTT if TEST_KCONFIG && MODULE_ZTIMER
cpu/fe310: model Kconfig
2021-09-28 16:18:15 +02:00
cpu/fe310: add Kconfig configuration
2020-06-23 21:39:14 +02:00
config CPU_MODEL_FE310_G000
bool
select CPU_FAM_FE310
config CPU_MODEL_FE310_G002
bool
select CPU_FAM_FE310
## Definition of specific features
config HAS_CPU_FE310
bool
help
Indicates that a 'fe310' cpu is being used.
config CPU_FAM
default "fe310" if CPU_FAM_FE310
config CPU_MODEL
default "fe310_g000" if CPU_MODEL_FE310_G000
default "fe310_g002" if CPU_MODEL_FE310_G002
config CPU
default "fe310" if CPU_FAM_FE310
cpu/fe310: move clock Kconfig to cpu
2020-12-15 23:12:06 +01:00
cpu/fe310: add CPU_CORE information
2021-09-22 15:51:54 +02:00
config CPU_CORE
default "rv32imac" if CPU_CORE_RV32IMAC
cpu/fe310: move clock Kconfig to cpu
2020-12-15 23:12:06 +01:00
rsource "Kconfig.clk"
cpu/fe310: model Kconfig
2021-09-28 16:18:15 +02:00
rsource "periph/Kconfig"
rsource "vendor/Kconfig"
riscv_common: Refactor common fe310 code to riscv_common
2020-09-09 21:37:15 +02:00
source "$(RIOTCPU)/riscv_common/Kconfig"
Copy Permalink