On 04-May-2004 Takashi Iwai wrote:
After a lot of cleanups and coding style changes, my driver still has some
things that must be fixed properly. Busy-waits are one of those.
The most used busy-waits have a timeout of 10ms and 100ms and they are
called with a spinlock_irq held or from the
At Wed, 28 Apr 2004 23:09:36 +0200,
Giuliano Pochini wrote:
After a lot of cleanups and coding style changes, my driver still has some
things that must be fixed properly. Busy-waits are one of those.
The most used busy-waits have a timeout of 10ms and 100ms and they are
called with a
After a lot of cleanups and coding style changes, my driver still has some
things that must be fixed properly. Busy-waits are one of those.
The most used busy-waits have a timeout of 10ms and 100ms and they are
called with a spinlock_irq held or from the irq handler. With my card
the longest
