> Since these chips touch many different parts of traditionally separate > driver areas, how should the drivers be structured so that they can > all talk to the chip? Should the low level communications routines for > the chip live in a library which all the drivers could use?
Probably yes. And that if possible should manage all the locking. Thats roughly how the majority of drivers do it. Some export the lock from base code and inline the accessors depending how complex it is. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
