The GPIO utils in FPP use a combination of /sys/devices/platform/ocp/ocp:%s_pinmux/state and /sys/class/gpio/gpio%u/ locations to configure the pin in various ways. See:
https://github.com/FalconChristmas/fpp/blob/master/src/util/BBBUtils.cpp#L228 Some of it is a bit complex as some pins may need to boot up in i2c mode but then be flipped to gpio/out. The idea of using libgpiod is "ok" but doesn't allow configuring the internal pull ups for the input (at least until kernel 5.4 and a newer version of libgpiod) Dan On Friday, June 5, 2020 at 7:06:48 AM UTC-4, Drew Fustini wrote: > > On Fri, Jun 5, 2020 at 6:58 AM TJF <jeli.f...@gmail.com <javascript:>> > wrote: > > > > Am Mittwoch, 3. Juni 2020 16:27:38 UTC+2 schrieb RobertCNelson: > >> > >> The proper way is to use libgpiod tools such as gpioset ;) > > > > > > The proper way is to use libpruio and do pinmuxing single source in the > code ;) > > > > pruio_gpio_setValue(io, P9_11, [0,1]); > > How does the library change the pinmux during runtime? > > Does it use /sys/devices/platform/ocp/ocp:P9_11_pinmux/state? (which > is created by bone-pinmux-helper) > > thanks, > drew > -- 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/22759d88-d8da-431b-bf4c-6ada232fefc6o%40googlegroups.com.
