User space <==> kernel space for device wakeups.

[Jeshwanth Kumar N K]

On Wed, Oct 8, 2014 at 10:08 PM, Greg Kroah-Hartman <greg at kroah.com> wrote:

>
> A: No.
> Q: Should I include quotations after my reply?
>
> http://daringfireball.net/2007/07/on_top
>
> On Wed, Oct 08, 2014 at 10:01:43PM +0530, Jeshwanth Kumar N K wrote:
> > Greg, then what will you suggest for my case? I mean any alternative ?
>
> What "case"?  What problem are you trying to solve?
>
> greg k-h
>


Oh, correct. 2nd time I am warned on this (may be practise by using
outlook). Will reply bottom now onwards - sorry.

My case was: I have a hall sensor connected to Beaglebone black, And
Userspace needed a wakeup once the interrupt occur (example: every rising
edge of GPIO). Before that, the program will register (ioctl) the User
space task pointer with my kernel module, then my kernel module start
sending signal for every interrupt occur. We can consider roughly around
100 to 200 interrupts per second maximum. ( I have not done this, but may
be we can consider kernel will get notified when userspace program stops.
so that it will not send any signal). So for this case, any other
alternative implementation ?

Thanks

-- 
Regards
Jeshwanth Kumar N K
Bangalore, India
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20141008/6189aa67/attachment.html