Makes sense. Thanks for your ideas. Is there a header file, along the lines of sys_mcspi.h that Jason provided, that you use for the GPIO?
Kirk On Wednesday, September 7, 2016 at 2:28:43 PM UTC-7, Charles Steinkuehler wrote: > > On 9/7/2016 1:02 PM, Kirk wrote: > > > > What is the recommended way to access NON PRU GPIO pins? > > > > I'm asking because I'm working with a custom cape board on the > Beaglebone Black > > that has already been built. > > And I'm trying to move some time critical code to the PRU. > > I don't think all the GPIO pins that are used are in the group of PRU > GPIO pins. > > IMHO it works best if you setup the GPIO banks with Linux, then use > the PRU to twiddle the output bits using the set and clear registers > in the GPIO bank. That way you don't have to worry about any sort of > locking to insure consistent updates. Note the Linux side also needs > to use the set/clear registers for output updates (and not a > read-modify-write sequence) to insure no updates get lost. > > -- > Charles Steinkuehler > cha...@steinkuehler.net <javascript:> > -- 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/323348a0-6800-4b5d-9450-d08d5a364f45%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
