| ??? 06/30/10 06:06 Read: times |
#176988 - So don't trample over shared resources, then! Responding to: ???'s previous message |
The driver should affect only the specific module, and no others.
You have a separate driver (or drivers) for the timer(s). Your interface specification will have to say something like, "the required clock must be suitably configured prior to calling this routine", and there will have to be some kind of "parameter" - whether runtime of preprocessor - to choose the clock source. You could try looking at the "Standard Peripheral Libraries" that ST provide for their chips... You might also want to take a look at this thread: http://www.8052.com/forum/read/176494 |
| Topic | Author | Date |
| Guidelines for periphrial drivers | 01/01/70 00:00 | |
| My recommendation... | 01/01/70 00:00 | |
| Advantage | 01/01/70 00:00 | |
| So don't trample over shared resources, then! | 01/01/70 00:00 | |
| Maybe someone have developed/modified | 01/01/70 00:00 | |
| SMBus uses 2 timers on F34x series | 01/01/70 00:00 | |
well ... | 01/01/70 00:00 |