> > Thank you for sharing this CH32V30x porting repository. > For anyone following along, this was an accident. The "real" repo (to which I'm about to commit more stuff) is at https://github.com/robertlipe/incubator-nuttx
> I think the right way to handle the GPIO is like STM32 and other > arches do, not inside the menuconfig. > I'll see how that works. menuconfig clearly doesn't scale to this level. Any thoughts on the idea of sharing, say, *gpio.c or *uart.c with the STM32 if that's at all possible? I see both sides. > Some time ago someone suggested using menuconfig to select the > function of each pin of the MCU, but although the idea is cool, it is > not feasible. > Agreed. > Each architecture has its own rules to select the pins function and > Kconfig is not to flexible to create complex logic for pin mux, etc. > It is better to do it on C code using macros and preprocessing. > Lup and I certainly ran into this even on BL602 It's why we have the (out-of-tree) GPIO expander and we had only 24 GPIOs. RJL
