2019-04-06 21:08:09 +08:00
|
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
|
|
2018-11-29 05:23:51 +08:00
|
|
|
if BOARD_RV32M1_VEGA
|
2019-09-19 18:35:00 +08:00
|
|
|
comment "RV32M1 board Kconfig.defconfig"
|
2018-11-29 05:23:51 +08:00
|
|
|
|
|
|
|
|
config BOARD
|
|
|
|
|
default "rv32m1_vega_ri5cy" if SOC_OPENISA_RV32M1_RI5CY
|
|
|
|
|
default "rv32m1_vega_zero_riscy" if SOC_OPENISA_RV32M1_ZERO_RISCY
|
|
|
|
|
|
|
|
|
|
if UART_RV32M1_LPUART
|
|
|
|
|
|
|
|
|
|
config UART_RV32M1_LPUART_0
|
kconfig: Use 'default' instead of 'def_bool' in Kconfig.defconfig files
Same deal as in commit 4638652214 ("Kconfig: Use 'default' instead of
'def_bool' in Kconfig.defconfig files"), fixing new stuff that got
introduced since then.
Some symbols, like ALTERA_AVALON_PIO, are only defined in
Kconfig.defconfig files, and so need the def_bool.
Motivation (from the note at the end of
guides/kconfig/index.html#common-shorthands):
For a symbol defined in multiple locations (e.g., in a Kconfig.defconfig
file in Zephyr), it is best to only give the symbol type for the "base"
definition of the symbol, and to use 'default' (instead of 'def_<type>'
value) for the remaining definitions. That way, if the base definition
of the symbol is removed, the symbol ends up without a type, which
generates a warning that points to the other definitions. That makes the
extra definitions easier to discover and remove.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-18 19:29:31 +08:00
|
|
|
default y if UART_CONSOLE
|
2018-11-29 05:23:51 +08:00
|
|
|
|
|
|
|
|
endif # UART_RV32M1
|
|
|
|
|
|
|
|
|
|
if PINMUX_RV32M1
|
|
|
|
|
|
|
|
|
|
config PINMUX_RV32M1_PORTA
|
kconfig: Use 'default' instead of 'def_bool' in Kconfig.defconfig files
Same deal as in commit 4638652214 ("Kconfig: Use 'default' instead of
'def_bool' in Kconfig.defconfig files"), fixing new stuff that got
introduced since then.
Some symbols, like ALTERA_AVALON_PIO, are only defined in
Kconfig.defconfig files, and so need the def_bool.
Motivation (from the note at the end of
guides/kconfig/index.html#common-shorthands):
For a symbol defined in multiple locations (e.g., in a Kconfig.defconfig
file in Zephyr), it is best to only give the symbol type for the "base"
definition of the symbol, and to use 'default' (instead of 'def_<type>'
value) for the remaining definitions. That way, if the base definition
of the symbol is removed, the symbol ends up without a type, which
generates a warning that points to the other definitions. That makes the
extra definitions easier to discover and remove.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-18 19:29:31 +08:00
|
|
|
default y
|
2018-11-29 05:23:51 +08:00
|
|
|
|
|
|
|
|
config PINMUX_RV32M1_PORTB
|
kconfig: Use 'default' instead of 'def_bool' in Kconfig.defconfig files
Same deal as in commit 4638652214 ("Kconfig: Use 'default' instead of
'def_bool' in Kconfig.defconfig files"), fixing new stuff that got
introduced since then.
Some symbols, like ALTERA_AVALON_PIO, are only defined in
Kconfig.defconfig files, and so need the def_bool.
Motivation (from the note at the end of
guides/kconfig/index.html#common-shorthands):
For a symbol defined in multiple locations (e.g., in a Kconfig.defconfig
file in Zephyr), it is best to only give the symbol type for the "base"
definition of the symbol, and to use 'default' (instead of 'def_<type>'
value) for the remaining definitions. That way, if the base definition
of the symbol is removed, the symbol ends up without a type, which
generates a warning that points to the other definitions. That makes the
extra definitions easier to discover and remove.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-18 19:29:31 +08:00
|
|
|
default y
|
2018-11-29 05:23:51 +08:00
|
|
|
|
|
|
|
|
config PINMUX_RV32M1_PORTC
|
kconfig: Use 'default' instead of 'def_bool' in Kconfig.defconfig files
Same deal as in commit 4638652214 ("Kconfig: Use 'default' instead of
'def_bool' in Kconfig.defconfig files"), fixing new stuff that got
introduced since then.
Some symbols, like ALTERA_AVALON_PIO, are only defined in
Kconfig.defconfig files, and so need the def_bool.
Motivation (from the note at the end of
guides/kconfig/index.html#common-shorthands):
For a symbol defined in multiple locations (e.g., in a Kconfig.defconfig
file in Zephyr), it is best to only give the symbol type for the "base"
definition of the symbol, and to use 'default' (instead of 'def_<type>'
value) for the remaining definitions. That way, if the base definition
of the symbol is removed, the symbol ends up without a type, which
generates a warning that points to the other definitions. That makes the
extra definitions easier to discover and remove.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-18 19:29:31 +08:00
|
|
|
default y
|
2018-11-29 05:23:51 +08:00
|
|
|
|
|
|
|
|
config PINMUX_RV32M1_PORTD
|
kconfig: Use 'default' instead of 'def_bool' in Kconfig.defconfig files
Same deal as in commit 4638652214 ("Kconfig: Use 'default' instead of
'def_bool' in Kconfig.defconfig files"), fixing new stuff that got
introduced since then.
Some symbols, like ALTERA_AVALON_PIO, are only defined in
Kconfig.defconfig files, and so need the def_bool.
Motivation (from the note at the end of
guides/kconfig/index.html#common-shorthands):
For a symbol defined in multiple locations (e.g., in a Kconfig.defconfig
file in Zephyr), it is best to only give the symbol type for the "base"
definition of the symbol, and to use 'default' (instead of 'def_<type>'
value) for the remaining definitions. That way, if the base definition
of the symbol is removed, the symbol ends up without a type, which
generates a warning that points to the other definitions. That makes the
extra definitions easier to discover and remove.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-18 19:29:31 +08:00
|
|
|
default y
|
2018-11-29 05:23:51 +08:00
|
|
|
|
|
|
|
|
config PINMUX_RV32M1_PORTE
|
kconfig: Use 'default' instead of 'def_bool' in Kconfig.defconfig files
Same deal as in commit 4638652214 ("Kconfig: Use 'default' instead of
'def_bool' in Kconfig.defconfig files"), fixing new stuff that got
introduced since then.
Some symbols, like ALTERA_AVALON_PIO, are only defined in
Kconfig.defconfig files, and so need the def_bool.
Motivation (from the note at the end of
guides/kconfig/index.html#common-shorthands):
For a symbol defined in multiple locations (e.g., in a Kconfig.defconfig
file in Zephyr), it is best to only give the symbol type for the "base"
definition of the symbol, and to use 'default' (instead of 'def_<type>'
value) for the remaining definitions. That way, if the base definition
of the symbol is removed, the symbol ends up without a type, which
generates a warning that points to the other definitions. That makes the
extra definitions easier to discover and remove.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-18 19:29:31 +08:00
|
|
|
default y if RV32M1_INTMUX
|
2018-11-29 05:23:51 +08:00
|
|
|
|
|
|
|
|
endif # PINMUX_RV32M1
|
|
|
|
|
|
|
|
|
|
if GPIO_RV32M1
|
|
|
|
|
|
|
|
|
|
config GPIO_RV32M1_PORTA
|
kconfig: Use 'default' instead of 'def_bool' in Kconfig.defconfig files
Same deal as in commit 4638652214 ("Kconfig: Use 'default' instead of
'def_bool' in Kconfig.defconfig files"), fixing new stuff that got
introduced since then.
Some symbols, like ALTERA_AVALON_PIO, are only defined in
Kconfig.defconfig files, and so need the def_bool.
Motivation (from the note at the end of
guides/kconfig/index.html#common-shorthands):
For a symbol defined in multiple locations (e.g., in a Kconfig.defconfig
file in Zephyr), it is best to only give the symbol type for the "base"
definition of the symbol, and to use 'default' (instead of 'def_<type>'
value) for the remaining definitions. That way, if the base definition
of the symbol is removed, the symbol ends up without a type, which
generates a warning that points to the other definitions. That makes the
extra definitions easier to discover and remove.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-18 19:29:31 +08:00
|
|
|
default y
|
2018-11-29 05:23:51 +08:00
|
|
|
|
|
|
|
|
config GPIO_RV32M1_PORTB
|
kconfig: Use 'default' instead of 'def_bool' in Kconfig.defconfig files
Same deal as in commit 4638652214 ("Kconfig: Use 'default' instead of
'def_bool' in Kconfig.defconfig files"), fixing new stuff that got
introduced since then.
Some symbols, like ALTERA_AVALON_PIO, are only defined in
Kconfig.defconfig files, and so need the def_bool.
Motivation (from the note at the end of
guides/kconfig/index.html#common-shorthands):
For a symbol defined in multiple locations (e.g., in a Kconfig.defconfig
file in Zephyr), it is best to only give the symbol type for the "base"
definition of the symbol, and to use 'default' (instead of 'def_<type>'
value) for the remaining definitions. That way, if the base definition
of the symbol is removed, the symbol ends up without a type, which
generates a warning that points to the other definitions. That makes the
extra definitions easier to discover and remove.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-18 19:29:31 +08:00
|
|
|
default y if RV32M1_INTMUX
|
2018-11-29 05:23:51 +08:00
|
|
|
|
|
|
|
|
config GPIO_RV32M1_PORTC
|
kconfig: Use 'default' instead of 'def_bool' in Kconfig.defconfig files
Same deal as in commit 4638652214 ("Kconfig: Use 'default' instead of
'def_bool' in Kconfig.defconfig files"), fixing new stuff that got
introduced since then.
Some symbols, like ALTERA_AVALON_PIO, are only defined in
Kconfig.defconfig files, and so need the def_bool.
Motivation (from the note at the end of
guides/kconfig/index.html#common-shorthands):
For a symbol defined in multiple locations (e.g., in a Kconfig.defconfig
file in Zephyr), it is best to only give the symbol type for the "base"
definition of the symbol, and to use 'default' (instead of 'def_<type>'
value) for the remaining definitions. That way, if the base definition
of the symbol is removed, the symbol ends up without a type, which
generates a warning that points to the other definitions. That makes the
extra definitions easier to discover and remove.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-18 19:29:31 +08:00
|
|
|
default y if RV32M1_INTMUX
|
2018-11-29 05:23:51 +08:00
|
|
|
|
|
|
|
|
config GPIO_RV32M1_PORTD
|
kconfig: Use 'default' instead of 'def_bool' in Kconfig.defconfig files
Same deal as in commit 4638652214 ("Kconfig: Use 'default' instead of
'def_bool' in Kconfig.defconfig files"), fixing new stuff that got
introduced since then.
Some symbols, like ALTERA_AVALON_PIO, are only defined in
Kconfig.defconfig files, and so need the def_bool.
Motivation (from the note at the end of
guides/kconfig/index.html#common-shorthands):
For a symbol defined in multiple locations (e.g., in a Kconfig.defconfig
file in Zephyr), it is best to only give the symbol type for the "base"
definition of the symbol, and to use 'default' (instead of 'def_<type>'
value) for the remaining definitions. That way, if the base definition
of the symbol is removed, the symbol ends up without a type, which
generates a warning that points to the other definitions. That makes the
extra definitions easier to discover and remove.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-18 19:29:31 +08:00
|
|
|
default y if RV32M1_INTMUX
|
2018-11-29 05:23:51 +08:00
|
|
|
|
|
|
|
|
config GPIO_RV32M1_PORTE
|
kconfig: Use 'default' instead of 'def_bool' in Kconfig.defconfig files
Same deal as in commit 4638652214 ("Kconfig: Use 'default' instead of
'def_bool' in Kconfig.defconfig files"), fixing new stuff that got
introduced since then.
Some symbols, like ALTERA_AVALON_PIO, are only defined in
Kconfig.defconfig files, and so need the def_bool.
Motivation (from the note at the end of
guides/kconfig/index.html#common-shorthands):
For a symbol defined in multiple locations (e.g., in a Kconfig.defconfig
file in Zephyr), it is best to only give the symbol type for the "base"
definition of the symbol, and to use 'default' (instead of 'def_<type>'
value) for the remaining definitions. That way, if the base definition
of the symbol is removed, the symbol ends up without a type, which
generates a warning that points to the other definitions. That makes the
extra definitions easier to discover and remove.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-18 19:29:31 +08:00
|
|
|
default y if RV32M1_INTMUX
|
2018-11-29 05:23:51 +08:00
|
|
|
|
|
|
|
|
endif # GPIO_RV32M1
|
|
|
|
|
|
|
|
|
|
if SERIAL
|
|
|
|
|
|
|
|
|
|
config UART_RV32M1_LPUART
|
kconfig: Use 'default' instead of 'def_bool' in Kconfig.defconfig files
Same deal as in commit 4638652214 ("Kconfig: Use 'default' instead of
'def_bool' in Kconfig.defconfig files"), fixing new stuff that got
introduced since then.
Some symbols, like ALTERA_AVALON_PIO, are only defined in
Kconfig.defconfig files, and so need the def_bool.
Motivation (from the note at the end of
guides/kconfig/index.html#common-shorthands):
For a symbol defined in multiple locations (e.g., in a Kconfig.defconfig
file in Zephyr), it is best to only give the symbol type for the "base"
definition of the symbol, and to use 'default' (instead of 'def_<type>'
value) for the remaining definitions. That way, if the base definition
of the symbol is removed, the symbol ends up without a type, which
generates a warning that points to the other definitions. That makes the
extra definitions easier to discover and remove.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-18 19:29:31 +08:00
|
|
|
default y
|
2018-11-29 05:23:51 +08:00
|
|
|
|
|
|
|
|
endif # SERIAL
|
|
|
|
|
|
2019-04-03 23:21:51 +08:00
|
|
|
if I2C
|
|
|
|
|
|
|
|
|
|
config I2C_0
|
2019-10-24 14:13:13 +08:00
|
|
|
default y
|
2019-04-03 23:21:51 +08:00
|
|
|
|
|
|
|
|
config I2C_3
|
2019-10-24 14:13:13 +08:00
|
|
|
default y if RV32M1_INTMUX
|
2019-04-03 23:21:51 +08:00
|
|
|
|
|
|
|
|
endif # I2C
|
|
|
|
|
|
2019-08-22 01:56:57 +08:00
|
|
|
if SPI
|
|
|
|
|
|
|
|
|
|
config SPI_1
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
endif # SPI
|
|
|
|
|
|
2019-09-19 18:35:00 +08:00
|
|
|
if BT
|
|
|
|
|
|
|
|
|
|
config BT_CTLR
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config RV32M1_INTMUX_CHANNEL_2
|
|
|
|
|
default n
|
|
|
|
|
|
|
|
|
|
config RV32M1_INTMUX_CHANNEL_3
|
|
|
|
|
default n
|
|
|
|
|
|
|
|
|
|
endif # BT
|
|
|
|
|
|
2018-11-29 05:23:51 +08:00
|
|
|
endif # BOARD_RV32M1_VEGA
|
