On Fri, Mar 27, 2020 at 11:46 AM Drew Fustini <pdp7p...@gmail.com> wrote:
> On Fri, Mar 27, 2020 at 4:48 PM John Allwine <j...@allwinedesigns.com> > wrote: > > > > That was it! gpioget gpiochip3 10 worked. > > It would be interesting to know if libgpiod proves fast enough for > your application. It has C++ and Python bindings that allow you to > set and get multiple lines on a gpiochip with a single ioctl(). > > I am in communication with Bartosz, who made the libgpiod userspace > library and utilities, and Linus Walleij who created the gpiod > interface (which includes the gpiochip character devices). They both > seem open minded to improving interfaces to address real-world use > cases. > Personally. I think trying to toggle a GPIO as fast as possible in Linux is the wrong way to go about it. According to what I've read(and I have no personal desire to test it). An empty ioctl() has 63ns latency. Add that on top of gpiod's time. Then it starts to add up. Not to mention: how proficient a given developer is when writing performant code. So, for doing anything blazing fast, we're back full circle. However, I think it would be better to use/buy hardware specialized for the task at hand. With that said, there is nothing wrong with experimenting. Until you let the blue smoke out. . . -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORptFxx%3DHy7Rxi085HzUwXMnv4oc1t_N6pO%3DrmqQZDngEQ%40mail.gmail.com.
