Well, then how do we make sure the GPIOs are muxed on the pins? The "normal" way to access GPIOs (via /sys/class/gpio) is not working in 3.11. Maybe due to the multiplexing? It worked fine in 3.7 stable, if it's any help.
/sys/kernel/debug/omap_mux is present, but it's empty. It is configured in the kernel build. I don't see how it can be enabled in device tree. On Thursday, October 24, 2013 2:07:34 PM UTC-4, RobertCNelson wrote: > > On Thu, Oct 24, 2013 at 1:02 PM, porkupan <vladimi...@gmail.com<javascript:>> > wrote: > > I suspect the problem is not GPIO, something else seems to be muxed into > the > > GPIO pins (maybe MMC2? But it is "disabled" in the DTS!). The GPIOs > are > > accessible from U-Boot (via "gpio" commands), but they are NOT > accessible > > from the Linux userspace. > > > > cd /sys/class/gpio > > echo 137 > export > > cd gpio137 > > echo "low" > direction > > > > no effect! The /sys/kernel/debug/omap_mux/sdmmc2_dat7 is not present, > so I > > cannot remux anything into the GPIO pins. > > omap_mux is not available in device tree.. > > Regards, > > -- > Robert Nelson > http://www.rcn-ee.com/ > -- 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. For more options, visit https://groups.google.com/groups/opt_out.
