Re: [riot-devel] Separating module drivers from physical pin configuration

2014-12-04 Thread Hauke Petersen
Hi Joakim, I also put some thought into this topic when designing the low-level interface. The problem I found most challenging was the heterogeneity of the different platforms. I found designing a central 'pin-muxing/config' module was too expensive in terms of resources compared to the actua

Re: [riot-devel] Separating module drivers from physical pin configuration

2014-12-01 Thread Joakim Gebart
Dear Thomas, Thank you for your feedback, see my response inline below. On Mon, Dec 1, 2014 at 11:32 AM, Thomas Eichinger wrote: > Dear Joakim, > >> On 30 Nov 2014, at 18:02, Joakim Gebart wrote: >> I would like to have a separate driver for setting up the CPU pin mux. >> That is, separate the

Re: [riot-devel] Separating module drivers from physical pin configuration

2014-12-01 Thread Thomas Eichinger
Dear Joakim, > On 30 Nov 2014, at 18:02, Joakim Gebart wrote: > I would like to have a separate driver for setting up the CPU pin mux. > That is, separate the CPU logic module drivers (such as SPI, I2C, UART > etc.) from the actual hardware ports and pins. You mean introducing a central point t

[riot-devel] Separating module drivers from physical pin configuration

2014-11-30 Thread Joakim Gebart
Dear developers, (This is probably only relevant to Cortex-M or other advanced MCUs; AVR etc. usually do not have much function muxing capability.) I would like to hear opinions on the following model: I would like to have a separate driver for setting up the CPU pin mux. That is, separate the CP