How to solve this scenario in Linux device drivers
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
How to solve this scenario in Linux device drivers
Hi All,
I have a scenario listing below, Please let me know how can i achieve this in linux.
If application program is trying to read data in a device/driver but data is not present at that moment, application should go into sleep/block state. Data came into device later and at this point of time how device/driver can tell to application or wakeup the application that now data is ready for read.
Please help me which mechanism will suitable to solve this in Linux, Thanks.
In the default case (no special open-time flags), the 'read' handler in your userspace driver should block (make the userspace thread sleep until data is available). If the userspace application has specified the O_ASYNC open()/fcntl() flag, raise a signal. If the userspace application has specified the O_NONBLOCK open()/fnctl() flag, return EWOULDBLOCK instead.
For examples, see the Linux Kernel Module Programming Guide, Blocking Processes section. There is even an example character driver in the guide.
In the default case (no special open-time flags), the 'read' handler in your userspace driver should block (make the userspace thread sleep until data is available). If the userspace application has specified the O_ASYNC open()/fcntl() flag, raise a signal. If the userspace application has specified the O_NONBLOCK open()/fnctl() flag, return EWOULDBLOCK instead.
For examples, see the Linux Kernel Module Programming Guide, Blocking Processes section. There is even an example character driver in the guide.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.