From: buyitian@gmail.com (buyitian)
To: kernelnewbies@lists.kernelnewbies.org
Subject: User space <==> kernel space for device wakeups.
Date: Thu, 9 Oct 2014 23:18:46 +0800 [thread overview]
Message-ID: <9249C191-ED02-41C4-B52D-AB2199E8C2A6@gmail.com> (raw)
In-Reply-To: <CAC-LjFsXqjP=caLmAPNJiwgDEAv-Jgwf-90hcW=EGEtQ91rLPw@mail.gmail.com>
> 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
Once kernel gets interrupt, it can use netlink to notify user space, if you are using Android, it is using UEVENT.
next prev parent reply other threads:[~2014-10-09 15:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 7:39 User space <==> kernel space for device wakeups manty kuma
2014-10-08 13:29 ` Greg KH
2014-10-08 15:44 ` Jeshwanth Kumar N K
2014-10-08 15:57 ` Kristof Provost
2014-10-08 16:25 ` Greg Kroah-Hartman
2014-10-08 16:31 ` Jeshwanth Kumar N K
2014-10-08 16:38 ` Greg Kroah-Hartman
2014-10-08 16:53 ` Jeshwanth Kumar N K
2014-10-08 17:32 ` Greg Kroah-Hartman
2014-10-08 17:47 ` Jeshwanth Kumar N K
2014-10-09 15:18 ` buyitian [this message]
2014-10-08 18:30 ` Jinqiang Zeng
2014-10-09 1:38 ` manty kuma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9249C191-ED02-41C4-B52D-AB2199E8C2A6@gmail.com \
--to=buyitian@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).