On Sun, Aug 12, 2001 at 03:24:08PM +0100, Philip Blundell wrote:
> Hmm, yeah. I think there is another way to solve the particular
> problem that seems to be at hand: don't own up to having a wakeup
> function when you first register your driver, call parport_claim()
> repeatedly in the loop rather than checking p_busy, and then poke
> your function into dev->wakeup once you are committed to using the
> port. Once probing is over the module use count should stop the
> driver getting unloaded at an inopportune moment.
Sounds like a hack, but it would prevent the locking problems I
suppose. I think I'd rather sort it out properly.
> I'll give it some more thought, but my initial reaction would be that no, it
> isn't reasonable to call parport_release or parport_unregister_device from
> your wakeup function.
Yeah, that's what I thought. I think that's the answer.
-- To unsubscribe, send mail to: email@example.com --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Mon Aug 13 2001 - 07:44:00 EDT