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
4e3151406c
RIOT/drivers/mtd/Kconfig

103 lines
2.4 KiB
Plaintext
Raw Normal View History

drivers/mtd: add module to Kconfig
2020-11-11 16:51:01 +01:00
# Copyright (c) 2020 HAW Hamburg
#
# 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.
#
drivers/mtd: fix Kconfig dependencies Currently implementations of the MTD api are selecting the module, this makes it easy for default backends to be selected. But the correct modeling is simply selecting the MTD api and then selecting a backend. BOARDs providing one of the backends can expose this and then that backend can be selected by default. There is also currently nothing preventing from using the MTD api with no backend since a mock backend can easily be provided as is done in all mtd tests.
2021-09-22 09:22:51 +02:00
config HAVE_MTD_AT24CXXX
bool
dirvers/mtd: use imply instead of select Using imply allow for user to deselect the default MTD backends
2021-09-29 10:13:51 +02:00
imply MODULE_MTD_AT24CXXX if MODULE_MTD
drivers/mtd: fix Kconfig dependencies Currently implementations of the MTD api are selecting the module, this makes it easy for default backends to be selected. But the correct modeling is simply selecting the MTD api and then selecting a backend. BOARDs providing one of the backends can expose this and then that backend can be selected by default. There is also currently nothing preventing from using the MTD api with no backend since a mock backend can easily be provided as is done in all mtd tests.
2021-09-22 09:22:51 +02:00
help
Indicates that a at24cxxx EEPROM MTD is present
config HAVE_MTD_AT25XXX
bool
dirvers/mtd: use imply instead of select Using imply allow for user to deselect the default MTD backends
2021-09-29 10:13:51 +02:00
imply MODULE_MTD_AT25XXX if MODULE_MTD
drivers/mtd: fix Kconfig dependencies Currently implementations of the MTD api are selecting the module, this makes it easy for default backends to be selected. But the correct modeling is simply selecting the MTD api and then selecting a backend. BOARDs providing one of the backends can expose this and then that backend can be selected by default. There is also currently nothing preventing from using the MTD api with no backend since a mock backend can easily be provided as is done in all mtd tests.
2021-09-22 09:22:51 +02:00
help
Indicates that a at25xxx SPI-EEPROM MTD is present
config HAVE_MTD_NATIVE
bool
dirvers/mtd: use imply instead of select Using imply allow for user to deselect the default MTD backends
2021-09-29 10:13:51 +02:00
imply MODULE_MTD_NATIVE if MODULE_MTD
drivers/mtd: fix Kconfig dependencies Currently implementations of the MTD api are selecting the module, this makes it easy for default backends to be selected. But the correct modeling is simply selecting the MTD api and then selecting a backend. BOARDs providing one of the backends can expose this and then that backend can be selected by default. There is also currently nothing preventing from using the MTD api with no backend since a mock backend can easily be provided as is done in all mtd tests.
2021-09-22 09:22:51 +02:00
help
Indicates that a native MTD is present.
drivers/mtd: fix module name for mtd_sdcard in Kconfig
2022-08-03 08:26:54 +02:00
config HAVE_MTD_SDCARD
drivers/mtd: fix Kconfig dependencies Currently implementations of the MTD api are selecting the module, this makes it easy for default backends to be selected. But the correct modeling is simply selecting the MTD api and then selecting a backend. BOARDs providing one of the backends can expose this and then that backend can be selected by default. There is also currently nothing preventing from using the MTD api with no backend since a mock backend can easily be provided as is done in all mtd tests.
2021-09-22 09:22:51 +02:00
bool
drivers/mtd: fix module name for mtd_sdcard in Kconfig
2022-08-03 08:26:54 +02:00
imply MODULE_MTD_SDCARD if MODULE_MTD
drivers/mtd: fix Kconfig dependencies Currently implementations of the MTD api are selecting the module, this makes it easy for default backends to be selected. But the correct modeling is simply selecting the MTD api and then selecting a backend. BOARDs providing one of the backends can expose this and then that backend can be selected by default. There is also currently nothing preventing from using the MTD api with no backend since a mock backend can easily be provided as is done in all mtd tests.
2021-09-22 09:22:51 +02:00
help
Indicates that a sdcard MTD is present
config HAVE_MTD_SPI_NOR
bool
dirvers/mtd: use imply instead of select Using imply allow for user to deselect the default MTD backends
2021-09-29 10:13:51 +02:00
imply MODULE_MTD_SPI_NOR if MODULE_MTD
drivers/mtd: fix Kconfig dependencies Currently implementations of the MTD api are selecting the module, this makes it easy for default backends to be selected. But the correct modeling is simply selecting the MTD api and then selecting a backend. BOARDs providing one of the backends can expose this and then that backend can be selected by default. There is also currently nothing preventing from using the MTD api with no backend since a mock backend can easily be provided as is done in all mtd tests.
2021-09-22 09:22:51 +02:00
help
Indicates that a spi-nor MTD is present
cpu/sam0_common: add SD Host Controller implementation
2022-03-18 12:35:05 +01:00
config HAVE_SAM0_SDHC
bool
imply MODULE_SAM0_SDHC if MODULE_MTD
help
Indicates that a SAM0 SD Host Controller MTD is present
drivers/mtd: fix Kconfig dependencies Currently implementations of the MTD api are selecting the module, this makes it easy for default backends to be selected. But the correct modeling is simply selecting the MTD api and then selecting a backend. BOARDs providing one of the backends can expose this and then that backend can be selected by default. There is also currently nothing preventing from using the MTD api with no backend since a mock backend can easily be provided as is done in all mtd tests.
2021-09-22 09:22:51 +02:00
config HAVE_MTD_SPI_MCI
bool
dirvers/mtd: use imply instead of select Using imply allow for user to deselect the default MTD backends
2021-09-29 10:13:51 +02:00
imply MODULE_MTD_MCI if MODULE_MTD
drivers/mtd: fix Kconfig dependencies Currently implementations of the MTD api are selecting the module, this makes it easy for default backends to be selected. But the correct modeling is simply selecting the MTD api and then selecting a backend. BOARDs providing one of the backends can expose this and then that backend can be selected by default. There is also currently nothing preventing from using the MTD api with no backend since a mock backend can easily be provided as is done in all mtd tests.
2021-09-22 09:22:51 +02:00
help
Indicates that a Multimedia Card Interface (MCI) MTD is present
menuconfig MODULE_MTD
drivers/mtd: add module to Kconfig
2020-11-11 16:51:01 +01:00
bool "Memory Technology Device interface (MTD)"
depends on TEST_KCONFIG
drivers/mtd: fix Kconfig dependencies Currently implementations of the MTD api are selecting the module, this makes it easy for default backends to be selected. But the correct modeling is simply selecting the MTD api and then selecting a backend. BOARDs providing one of the backends can expose this and then that backend can be selected by default. There is also currently nothing preventing from using the MTD api with no backend since a mock backend can easily be provided as is done in all mtd tests.
2021-09-22 09:22:51 +02:00
if MODULE_MTD
menu "MTD Interefaces"
config MODULE_MTD_SPI_NOR
bool "MTD interface for SPI NOR Flash"
depends on HAS_PERIPH_SPI
select MODULE_PERIPH_SPI
config MODULE_MTD_FLASHPAGE
bool "MTD interface for Flashpage"
depends on HAS_PERIPH_FLASHPAGE
depends on HAS_PERIPH_FLASHPAGE_PAGEWISE
select MODULE_PERIPH_FLASHPAGE
select MODULE_PERIPH_FLASHPAGE_PAGEWISE
help
Driver for internal flash devices implementing flashpage interface.
config MODULE_MTD_NATIVE
bool "MTD native driver"
depends on NATIVE_OS_LINUX
config MODULE_MTD_AT24CXXX
bool "MTD implementation for AT24CXXX"
depends on MODULE_AT24CXXX
config MODULE_MTD_AT25XXX
bool "MTD implementation for AT25XXX"
depends on MODULE_AT25XXX
config MODULE_MTD_MCI
bool "MTD interface for LPC23XX MCI"
depends on CPU_FAM_LPC23XX
select MODULE_MCI
config MODULE_MTD_SDCARD
bool "MTD interface for SPI SD-Card"
depends on MODULE_SDCARD_SPI
cpu/sam0_common: add SD Host Controller implementation
2022-03-18 12:35:05 +01:00
config MODULE_SAM0_SDHC
bool "MTD interface for SAM0 SD Host Controller"
depends on CPU_COMMON_SAM0
drivers/mtd: fix Kconfig dependencies Currently implementations of the MTD api are selecting the module, this makes it easy for default backends to be selected. But the correct modeling is simply selecting the MTD api and then selecting a backend. BOARDs providing one of the backends can expose this and then that backend can be selected by default. There is also currently nothing preventing from using the MTD api with no backend since a mock backend can easily be provided as is done in all mtd tests.
2021-09-22 09:22:51 +02:00
endmenu # MTD Interfacs
config MODULE_MTD_WRITE_PAGE
bool "MTD write page API"
endif
Copy Permalink