OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/drivers/interrupt_controller/Kconfig.rv32m1

68 lines
1.6 KiB
Plaintext
Raw Permalink Normal View History

kconfig: Clean up header comments and make them consistent Use this short header style in all Kconfig files: # <description> # <copyright> # <license> ... Also change all <description>s from # Kconfig[.extension] - Foo-related options to just # Foo-related options It's clear enough that it's about Kconfig. The <description> cleanup was done with this command, along with some manual cleanup (big letter at the start, etc.) git ls-files '*Kconfig*' | \ xargs sed -i -E '1 s/#\s*Kconfig[\w.-]*\s*-\s*/# /' Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-11-01 20:45:29 +08:00
# RV32M1 INTMUX config
interrupt_controller: RV32M1: add intmux driver / DT bindings Add a level 2 interrupt controller for the RV32M1 SoC. This uses the INTMUX peripheral. As a first customer, convert the timer driver over to using this, adding nodes for the LPTMR peripherals. This lets users select the timer instance they want to use, and what intmux channel they want to route its interrupt to, using DT overlays. Signed-off-by: Marti Bolivar <marti@foundries.io> Signed-off-by: Mike Scott <mike@foundries.io>
2018-11-25 17:41:38 +08:00
# Copyright (c) 2018 Foundries.io
# SPDX-License-Identifier: Apache-2.0
config RV32M1_INTMUX
bool "OpenISA RV32M1 INTMUX interrupt controller support"
drivers: intc: Update drivers to use devicetree Kconfig symbol Update intc drivers to use DT_HAS_<compat>_ENABLED Kconfig symbol to expose the driver and enable it by default based on devicetree. We remove 'depend on' Kconfig for symbols that would be implied by the devicetree node existing. Signed-off-by: Kumar Gala <galak@kernel.org>
2022-07-22 14:46:51 +08:00
default y
depends on DT_HAS_OPENISA_RV32M1_INTMUX_ENABLED
depends on MULTI_LEVEL_INTERRUPTS
interrupt_controller: RV32M1: add intmux driver / DT bindings Add a level 2 interrupt controller for the RV32M1 SoC. This uses the INTMUX peripheral. As a first customer, convert the timer driver over to using this, adding nodes for the LPTMR peripherals. This lets users select the timer instance they want to use, and what intmux channel they want to route its interrupt to, using DT overlays. Signed-off-by: Marti Bolivar <marti@foundries.io> Signed-off-by: Mike Scott <mike@foundries.io>
2018-11-25 17:41:38 +08:00
help
Select this option to enable support for the RV32M1 INTMUX
driver. This provides a level 2 interrupt controller for the SoC.
The INTMUX peripheral combines level 2 interrupts into
eight channels; each channel has its own level 1 interrupt to
the core.
if RV32M1_INTMUX
config RV32M1_INTMUX_INIT_PRIORITY
int "INTMUX driver initialization priority"
interrupt_controller: rv32m1: fix intmux driver initialization priority Use the RV32M1 SoC intmux driver initialization priority set by Kconfig. Change the default to match the default value of 40 used before. Signed-off-by: Henrik Brix Andersen <henrik@brixandersen.dk>
2019-04-09 03:26:06 +08:00
default 40
interrupt_controller: RV32M1: add intmux driver / DT bindings Add a level 2 interrupt controller for the RV32M1 SoC. This uses the INTMUX peripheral. As a first customer, convert the timer driver over to using this, adding nodes for the LPTMR peripherals. This lets users select the timer instance they want to use, and what intmux channel they want to route its interrupt to, using DT overlays. Signed-off-by: Marti Bolivar <marti@foundries.io> Signed-off-by: Mike Scott <mike@foundries.io>
2018-11-25 17:41:38 +08:00
help
Boot time initialization priority for INTMUX driver.
Don't change the default unless you know what you are doing.
config RV32M1_INTMUX_CHANNEL_0
bool "INTMUX channel 0"
help
Enable support for INTMUX channel 0.
config RV32M1_INTMUX_CHANNEL_1
bool "INTMUX channel 1"
help
Enable support for INTMUX channel 1.
boards: riscv: rv32m1: enable BT related configuration Specific SW defined BLE LL parameters need to be set if the user enables it on this platform. As such, conditionally enable them directly into the defconfig. INTMUX CH2 and CH3 are not available to be used if BT support is enabled on Vega, because they are used internally by the BLE SW LL Signed-off-by: David Leach <david.leach@nxp.com>
2019-09-19 18:35:00 +08:00
if !BT
interrupt_controller: RV32M1: add intmux driver / DT bindings Add a level 2 interrupt controller for the RV32M1 SoC. This uses the INTMUX peripheral. As a first customer, convert the timer driver over to using this, adding nodes for the LPTMR peripherals. This lets users select the timer instance they want to use, and what intmux channel they want to route its interrupt to, using DT overlays. Signed-off-by: Marti Bolivar <marti@foundries.io> Signed-off-by: Mike Scott <mike@foundries.io>
2018-11-25 17:41:38 +08:00
config RV32M1_INTMUX_CHANNEL_2
bool "INTMUX channel 2"
help
Enable support for INTMUX channel 2.
config RV32M1_INTMUX_CHANNEL_3
bool "INTMUX channel 3"
help
Enable support for INTMUX channel 3.
boards: riscv: rv32m1: enable BT related configuration Specific SW defined BLE LL parameters need to be set if the user enables it on this platform. As such, conditionally enable them directly into the defconfig. INTMUX CH2 and CH3 are not available to be used if BT support is enabled on Vega, because they are used internally by the BLE SW LL Signed-off-by: David Leach <david.leach@nxp.com>
2019-09-19 18:35:00 +08:00
endif # BT
interrupt_controller: RV32M1: add intmux driver / DT bindings Add a level 2 interrupt controller for the RV32M1 SoC. This uses the INTMUX peripheral. As a first customer, convert the timer driver over to using this, adding nodes for the LPTMR peripherals. This lets users select the timer instance they want to use, and what intmux channel they want to route its interrupt to, using DT overlays. Signed-off-by: Marti Bolivar <marti@foundries.io> Signed-off-by: Mike Scott <mike@foundries.io>
2018-11-25 17:41:38 +08:00
config RV32M1_INTMUX_CHANNEL_4
bool "INTMUX channel 4"
help
Enable support for INTMUX channel 4.
config RV32M1_INTMUX_CHANNEL_5
bool "INTMUX channel 5"
help
Enable support for INTMUX channel 5.
config RV32M1_INTMUX_CHANNEL_6
bool "INTMUX channel 6"
help
Enable support for INTMUX channel 6.
config RV32M1_INTMUX_CHANNEL_7
bool "INTMUX channel 7"
help
Enable support for INTMUX channel 7.
endif # RV32M1_INTMUX