When you are in intrrupt context you can not access the process data structure. I think *Completion variable* should solve your purpose. The task waits for signal by calling *wait_for_completion* and by calling *complete* you can wake-up all the waiting task. In your case you can call *complete* from interrupt handler. *Completion Variable* is a subset of semaphore but has low memory footprint. -Manish On Thu, Aug 20, 2009 at 5:43 PM, Shankar Ganesh <[email protected]>wrote:
> Hi Friends, > > I have an interrupt handler in my driver which is supposed to > wake-up/intimate user process to proceed . How do Linux supports this > mechanism ? > I have a choice of using select/poll in user space and implementing poll > fops in my driver. Is there any alternative better approach available? > > Thanks in Advance, > ShankarGanesh K . > > "The most beautiful thing we can experience is the mysterious. It is the > source of all true art and science." >
