> Those are sources of generic information passed to the drivers. Not > intrinsic data of the SoC (like its memory map). >
Then you say the problem was mixing sensitive memory map that breaks modularity if exposed with GPIO port addresses, absolute requirement for any GPIO subsystem No, I think the problem is somewhere else > > -----Original Message----- > From: Grr [mailto:gebbe...@gmail.com] > Sent: Saturday, February 06, 2021 7:12 AM > To: dev@nuttx.apache.org > Subject: Re: Proper handling of arch header files > > > It is very non-modular if it exposes internal data. Tha must be > > strictly avoided and prohibited in all cases. > > > > So you mean exposing STM32_BOARD_XTAL and STM32_SYSCLK_FREQUENCY is OK but > exposing board IO port address violates modularity > > That logic escapes me >
