On 24 January 2012 15:17, Sebastian Kuzminsky <[email protected]> wrote:
> If we get rid of the > pet_watchdog() function, I think we'd have to pet in both read() and write() > to cover all cases, and that'd be wasteful. It would be possible for the first of read() or write() (or read_gpio() or write_gpio() I suppose) to set a flag/mutex telling the other functions not to bother. I do agree that it seems worthwhile avoiding a double-strike as it is a full llio_write cycle unrelated to the "TRAM" reads/write process. > I like read() and write() waking up the watchdog, but i think i want to keep > pet_watchdog() to do the work. Given that you could have base-thread gpio-only reads and writes I think that is probably best. -- atp The idea that there is no such thing as objective truth is, quite simply, wrong. ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
