>>>--- linux/drivers/i2c/i2c-elektor.c.orig 2002-09-14 22:10:45.000000000 -0400
>>>+++ linux-2.5.34/drivers/i2c/i2c-elektor.c 2002-09-15 01:18:55.000000000 -0400
>>> int timeout = 2;
>>> if (irq > 0) {
>>>- cli();
>>>+ local_irq_disable();
>>> if (pcf_pending == 0) {
>>> interruptible_sleep_on_timeout(&pcf_wait, timeout*HZ );
>>> } else
>>> pcf_pending = 0;
>>>- sti();
>>>+ local_irq_enable();
>>> } else {
>>> udelay(100);
>>> }
>>this is _not_ the way to fix... use a proper spinlock
> You can't hold a spinlock and sleep though, was one of my points back
> in August. (Albert submitted a patch with all cli()/sti() converted
> to spin_lock_irqsave()/spin_unlock_irqrestore().)
whoops, you're right.
That follows along with my suggestion in another email, then :) use a
semaphore. The timeout can be handled with a kernel timer. The timeout
is clearly multiple seconds, so there's no fine grain involved.
AND, since the timeout is multiple seconds, the code should not be
disable interrupts for that long anyway.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
by