Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hi, i am executing a while in kernel space, and each 100 ms a timer interrupt is generated. so after finishing my work, how can i sleep in kernel until the next interrupt occur.
I may be a little beyond my expertise here, but isn't that a very strange thing to do? If I understand correctly, you would be denying all user space processes the ability to run while the kernel has gone to sleep waiting for a blasted interrupt! That said, in other, more primitive, processors I've worked on (looong time ago!) there were commands called things similar to "wait on interrupt" which would push all the usual info onto the stack (so it doesn't have to be pushed after receiving the interrupt) and then stop all processor activity until an interupt comes in (at which time normal processing resumes). I would suspect there is some such command in whatever processor you are using. But again, IMHO it sounds like a very questionable thing to do.
This is rather beyond anything I've done in Linux (so if this is a really stupid idea, be gentle ), but can you generate a signal in kernel mode and then have the user space program put itself to sleep and wake on the signal?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.