> Yeah, I need semaphore. This is a hw register that says when the hw > is ready to accept a new command. Code that wants to send commands has > to down the semaphore and then send it. When hw is ready to get a new > command, it sends and IRQ and the IRQ up()s the semaphore.
So you need a mutex not a semaphore > > Now, we don't want to hang on that down() forever if the hw spaces out. > If we get a timeout, we can try recovery actions (like resetting it, > for sake of being polite). Makes sense but you can also do that with mutexes, and its mutex_interruptible_timeout() you need I suspect ? Alan - 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/
