[Tracking]: modeling dependencies in Kconfig

[fjmolinas]

Description

These issues want to keep track of MODULES/PKG/CPU/BOARDs that are not modeled in Kconfig. Things already modeled at the time of this issue are not included.

Help is very welcomed, if you are already tackling something don't hesitate to list your name or an opened PR next to the item list. Initial work in branches is also welcome, someone else can take over later, so don't hesitate to reference either.

no exhaustive-list please extend:

• cpu:

  • cortex-m:
    • stm32
      • nucleo
      • others... boards/stm32-based: model Kconfig  #17374
    • nrf52 cpu/nrf52: initial kconfig modeling (no netif)  #16837
    • cc2538
    • efm32 cpu/efm32: model kconfig #16912
    • cc26x0_cc13x0 cpu/{cc26xx, cc13xx}: model kconfig #17236
    • cc26x2_cc13x2 cpu/{cc26xx, cc13xx}: model kconfig #17236
    • cc26x_cc13xx cpu/{cc26xx, cc13xx}: model kconfig #17236
    • kinetis cpu/kinetis: model kconfig #17235
    • lm4f120 (Not much required, board modelled in boards/ek-lm4f120xl: model kconfig #17237)
    • lpc1768 cpu/lpc1768: model kconfig #17238
    • nrf51 cpu/nrf51: model kconfig cpu/nrf51: model kconfig  #17274
    • nrf9160 cpu/nrf9160: add Kconfig dependencies #17291
    • qn908x cpu/qn908x: model kconfig #17277
    • rpx0xx (nothing required)
    • sam3 boards/common/arduino due: model kconfig #17240 (related boards)
    • samd21 boards/samd21-based: model Kconfig #17355 (related boards)
    • samd5x boards/adafruit-itsybitsy-m4: Model kconfig #17331
    • same54 .murdock: Add same54-xpro to kconfig tests #17255
    • saml1x (boards modelled in boards/common/saml1x: model kconfig #17263)
    • saml21 (boards modelled in boards/saml21-based: model kconfig #17270)
  • native
  • esp32 cpu/esp{32,8266}: model kconfig #17232
  • esp8266 cpu/esp{32,8266}: model kconfig #17232
  • avr cpu/avr8: model kconfig #16929
  • arm7
    • lpc23xx cpu/lpc23xx: model kconfig #17279
  • riscv cpu/riscv: model Kconfig #16909
  • mips (OBSOLETE)
  • msp430 cpu/msp430: add Kconfig #17290

• pkgs:

  • mynewt-core pkg/uwb*: add Kconfig dependency modelling #16780
  • uwb-core pkg/uwb*: add Kconfig dependency modelling #16780
  • uwb-dw1000 pkg/uwb*: add Kconfig dependency modelling #16780
  • ccn-lite
  • cmsis-dsp cpu/efm32: model kconfig #16912
  • cmsis-nn cpu/efm32: model kconfig #16912
  • cryptoauthlib pkg/cryptoauthlib: model in kconfig #18011
  • edhoc-c
  • esp8266_sdk cpu/esp{32,8266}: model kconfig #17232
  • fatfs
  • fido2_tests sys/fido2: model Kconfig #17435
  • flatbuffers pkg/tflite-micro: add support and deprecate tensorflow-lite #17908
  • gecko_sdk cpu/efm32: model kconfig #16912
  • jerryscript pkg/jerryscript: model in Kconfig #18012
  • libbase58 pkg/libbase58: add kconfig support #19623
  • littlefs
  • littlefs2
  • lua pkg/lua: model in kconfig #18017
  • lwext4
  • lwip
  • micropython pkg/micropython: model in Kconfig #19672
  • nimble
  • openthread pkg/openthread: model in kconfig #19671
  • openwsn
  • paho-mqtt
  • semtech-loramac pkg/semtech-loramac: model in Kconfig #18005
  • spiffs
  • tflite-micro pkg/tflite-micro: add support and deprecate tensorflow-lite #17908
  • tinydtls
  • wakaama
  • wolfssl

• sys:

  • can sys/can: model in kconfig #19675
  • ecc sys: model ecc, evtimer, pipe and shell_lock in kconfig #19636
  • evtimer sys: model ecc, evtimer, pipe and shell_lock in kconfig #19636
  • fuzzing
  • net
    • ieee802154 submac {dev,net}/ieee802154_*: add initial Kconfig modeling #16842
  • newlib_syscalls_default kconfig: introduce migration test in CI #14626 and 9557a9d
  • picolibc_syscalls_default cpu/riscv: model Kconfig #16909 9557a9d
  • pipe sys: model ecc, evtimer, pipe and shell_lock in kconfig #19636
  • puf_sram
  • riotboot
  • shell_lock sys: model ecc, evtimer, pipe and shell_lock in kconfig #19636
  • stdio:
    • stdio_nimble
    • stdio_null treewide: modify Kconfig symbol prefixes #14904
    • stdio_rtt boards: model nrf52 boards #17299
    • stdio_semihosting sys/stdio_semihosting: model in Kconfig #19651
    • stdio_uart treewide: modify Kconfig symbol prefixes #14904
    • stdio_udp
  • suit
  • universal_address
  • usb: Remodel the USB in Kconfig #19086
  • vfs: tests/vfs*: Model kconfig #19403
    • vfs_util

• drivers:

  • at86rf2xx drivers: model IEEE 802.15.4 devices in Kconfig #17789
  • at86rf215 drivers: model IEEE 802.15.4 devices in Kconfig #17789
  • atwinc15x0 drivers/atwinc15x0: add Kconfig #17382
  • cc1xxx_common
  • cc110x
  • cc2420 drivers: model IEEE 802.15.4 devices in Kconfig #17789
  • cst816s drivers/cst816s: add touch_dev interface + add Kconfig + migrate to ztimer #17459
  • dac_dds drivers/*/Kconfig: Cleanup of simple drivers #17669
  • dose drivers: model kconfig for Ethernet drivers #17739
  • enc28j60 drivers: model kconfig for Ethernet drivers #17739
  • encx24j600 drivers: model kconfig for Ethernet drivers #17739
  • ethos drivers: model kconfig for Ethernet drivers #17739
  • kw2xrf drivers: model IEEE 802.15.4 devices in Kconfig #17789
  • kw41zrf drivers: model IEEE 802.15.4 devices in Kconfig #17789
  • mrf24j40 drivers: model IEEE 802.15.4 devices in Kconfig #17789
  • netdev drivers: model kconfig for Ethernet drivers #17739
  • netdev_ieee802154_submac drivers: model IEEE 802.15.4 devices in Kconfig #17789
  • nrf24l01p drivers/nrf24l01p: model in kconfig #19650
  • nrf24l01p_ng
  • w5100 drivers: model kconfig for Ethernet drivers #17739
  • xbee

[fjmolinas]

Note AFAIK in sys most modules that are pending for modeling are related to networkin. Same goes for pkg and drivers

[fjmolinas]

@maribu any change you could take a look at avr? Do you seem to be doing a lot of work there?

[fjmolinas]

Since there is some discussion of eventually dropping MIPS it should be low priority.. (probably the same for MSP430)

[MrKevinWeiss]

Just to note that we would like to get all the cpus in for this release, this would allow us to stop testing select apps twice and use pure kconfig for dep resolution.

[MrKevinWeiss]

Just so it is written down somewhere. The configs we are using to set things for the STDIO_USB_ACM_CDC stuff I think will fail on apps that don't use stdio. They get hardcoded in by the .config file but they really should only be brought in if there is a MODULE_STDIO.

We will eventually have to address this (though maybe not now).

[Enoch247]

I wanted to make an offer to help out with kconfig. I'm pretty confident with Makefiles and kconfig's syntax. Any place in particular I should start?

[MrKevinWeiss]

Heck ya @Enoch247, if you didn't read the kconfig docs I would start with that.

Currently I am working on getting all boards (that are not deprecated) to run on some applications. There are still some boards that will not work on the approved applications list, but there are already PRs out there to fix it.

The next step would be to add more applications to the TEST_KCONFIG_TEST_ALLOWLIST, this will expose more modelling corner cases. Note that adding more applications will also increase the CI time so we didn't want to overdo it. Once we are confident that the modelling is correct with kconfig we can only build test with kconfig and skip the make dependency resolution, reducing the CI time.

Though I have been talking about it for a while, I also intend on documenting some design patterns that we want to use in kconfig, specifically targeting drivers that can be selected by "default" based modules such as SAUL_DEFAULT or TOUCH_DEV. There will be some work getting everything to the same standard once that comes in.

The final thing that is missing will be modelling the network dependencies, which will be pretty challenging as you need to understand the network stacks as well as kconfig. I image we will start working on that pretty soon. I know we all want to complete this migration, and it seems like things are picking up.

@leandrolanzieri @fjmolinas and I will be happy to answer any questions and provide help. The best thing you can do is document the questions and answers in a concise and add it to the docs. I know I have asked the same things from @leandrolanzieri several times already.

[Enoch247]

I finally had a chance to poke around on this. As a simple test, I tried make -C examples/saul menuconfig then played around with the shell's config symbols, then make all term. Everything worked as expected, so I don't really have any questions so far. I'm struggling to find any concrete task to sink my teeth into here. I noticed riotboot is on the checklist above and is an area I was tinkering with earlier today, so I could work on adding the appropriate Kconfig files for that if nothing else, unless you have something else you would prefer I start with.

When I do have questions, I figured I'd document them and the answers in a gist or something, then we can figure out how to put them into something more formal once I get a bit further into it. Unless you had something else in-mind.

[MrKevinWeiss]

I figured I'd document them and the answers in a gist or something

Perfect.

I have started a design patterns PR, we can probably add some things in there.

I haven't looked into riotboot, but keep in mind the networking is not yet modelled which may be a requirement for at least some of riotboot.

Other than that, good luck!

[aabadie]

I edited the issue with new items and marked the ones that are in progress or already done.

[benpicco]

As per the last VMA we decided to drop Kconfig, so this issue can now be closed.