> Dynamic pinmux changes on AM5x have issues specific to AM5x. > > For GPIO, accessing via register writes in userspace (/dev/mem) has no > more negative consequences than on AM3x or on any system running Linux for > that matter. Standard caveats apply. > > Ideally, we’d create a kernel module to avoid latency and keep kernel > resource control. This doesn’t have to be that complicated. In short of > that, the same old hacks will work fine on AM5x—just don’t touch the pinmux > without doing a LOT more digging. > > What is or how do I find the control register address for the AM5x? The system manual <https://github.com/beagleboard/beaglebone-ai/wiki/System-Reference-Manual#connector-p8> seems to list the offsets from the control register, but I'm unsure what that is.
> You my want to consider using libgpiod with the /dev/gpiochipN character >> device. You can get and set multiple lines in one syscall. >> >> The libgpiod tools are installed on the Debian image. >> >> More info: >> >> https://www.cnx-software.com/2017/11/03/learn-more-about-linuxs-new-gpio-user-space-subsystem-libgpiod/ >> > Thanks Drew! I'll give libgpiod a shot. -- 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/4f6c3135-a5a0-40fe-9c91-dd7fdfa74f1f%40googlegroups.com.
