All of lore.kernel.org
 help / color / mirror / Atom feed
From: <j.villena@ecler.com>
To: xenomai@xenomai.org
Subject: Using oob GPIO on RPi4B and evl_poll
Date: Fri, 3 Sep 2021 23:49:28 +0200	[thread overview]
Message-ID: <003a01d7a10d$9268d6b0$b73a8410$@ecler.com> (raw)

Hi all,

 

I am using the EVL Raspberry-PI-4 GPIO driver in oob mode for waiting for 4
GPI signals changes by monitoring raising and falling edges continuously.

 

The first version uses 4 diferent oob threads and it works as expected when
waiting forever in oob_read on each thread.

 

To optimize resources, I want to avoid to use the 4 threads approach, and I
want to create only one thread to handle all GPI functionality. Thus I have
added polling capabilities with evl_poll and related API to GPIO file
descriptors in only one thread.

 

At first it seems to work, but when I added another file descriptor to the
same polliing set (from an event flag group) the program freezes, and system
becomes unstable.

 

Then I noticed that in the "Polling file descriptors
<https://evlproject.org/core/user-api/poll/> " section of the EVL online
documentation, the GPIO real-time I/O driver is not listed in the
enumeration of pollable elements.

 

Is this true and the cause of the wrong behavior when using polled wait? If
yes, could it be easily fixed?

 

Thanks

 

 


             reply	other threads:[~2021-09-03 21:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 21:49 j.villena [this message]
2021-09-04  7:36 ` Using oob GPIO on RPi4B and evl_poll Philippe Gerum
2021-09-05 10:34   ` j.villena
2021-09-05 16:00     ` Philippe Gerum
2021-09-12 20:38       ` j.villena
2021-09-13  7:58         ` j.villena
2021-09-20  6:57           ` Philippe Gerum
2021-09-20  8:12             ` j.villena

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='003a01d7a10d$9268d6b0$b73a8410$@ecler.com' \
    --to=j.villena@ecler.com \
    --cc=xenomai@xenomai.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.