stbenn opened a new issue, #16202: URL: https://github.com/apache/nuttx/issues/16202
### Description For arch configuration, is it acceptable to use separate Kconfig files for logical blocks of the configuration? I am not proposing rework of already implemented Kconfig files, but would it be acceptable for new development? I experimented with the H5 arch and it appears to work just fine. I moved the peripheral selection menu options from `arch/arm/src/stm32h5/Kconfig` to a new file `arch/arm/src/stm32h5/Kconfig.periph_select`. Then replaced the original Kconfig options with `source arch/arm/src/stm32h5/Kconfig.periph_select`. The menu inside menuconfig remained the same, and it compiled without issue. Reason for wanting to do this: The H5 Kconfig is currently ~5k lines long, and will continue to expand as we add support for more peripherals. Encapsulating some of the options into separate files would make it easier to parse and validate configuration options. ### Verification - [x] I have verified before submitting the report. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
