PetervdPerk-NXP commented on issue #16415: URL: https://github.com/apache/nuttx/issues/16415#issuecomment-2926761185
I believe it ultimately comes down to clearly documenting the driver layers, so that everyone has a shared understanding of what the upper driver layer needs. > Have you ever considered this: A driver framework should be generic code that exposes sufficient functionality to the application layer while providing the simplest possible interfaces to the chip boot layer. Not everyone can design high-quality driver frameworks, but if the chip driver layer is kept simple enough, it will allow more people to contribute to chip driver development. There are countless chip drivers in the world that need to be implemented – only a few can produce high-quality ones. Therefore, we should lower the barrier for developing chip drivers. Everyone can do 1+1=2, but only a few can handle calculus. Your proposal is for all DMA related subsystems, which is out-of-scope I believe. Please keep a "simplest possible interfaces" and just focus on MMC/SDIO. Furthermore your proposed simplicity comes with a big cost, which is the use using dynamic memory allocation. I think should be avoided on a RTOS for resource-constrained devices. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
