From: greg@kroah.com (Greg Kroah-Hartman)
To: kernelnewbies@lists.kernelnewbies.org
Subject: User space <==> kernel space for device wakeups.
Date: Wed, 8 Oct 2014 10:32:37 -0700 [thread overview]
Message-ID: <20141008173237.GA15298@kroah.com> (raw)
In-Reply-To: <CAC-LjFsXqjP=caLmAPNJiwgDEAv-Jgwf-90hcW=EGEtQ91rLPw@mail.gmail.com>
On Wed, Oct 08, 2014 at 10:23:32PM +0530, Jeshwanth Kumar N K wrote:
> 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 ?
select() on the GPIO sysfs file instead of a custom ioctl?
And what do you do in userspace with that information?
greg k-h
next prev parent reply other threads:[~2014-10-08 17:32 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 [this message]
2014-10-08 17:47 ` Jeshwanth Kumar N K
2014-10-09 15:18 ` buyitian
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=20141008173237.GA15298@kroah.com \
--to=greg@kroah.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.