On Fri, Oct 27, 2017 at 1:27 PM, Robert Nelson <[email protected]> wrote: > Hi John, > > On Fri, Oct 27, 2017 at 1:20 PM, John Morris <[email protected]> wrote: >> To get Beagle GPIOs configured correctly at boot, is a custom overlay the >> right way to go? I want a bunch of the PocketBeagle pins configured as GPIO >> output low, but some of them start up in other modes with unwanted signals. > > So one of the difference between the BBB and the PocketBeagle, we have > 'config-pin' built-into the base *.dtb > > So if you want a dedicated use of a pin, you need to disable the > config-pin/cape-unversal pinmux: > > P1_02_pinmux { > status = "disabled"; > }; > > So this should work: > > https://gist.github.com/RobertCNelson/41ed096d96bede9617c0a1adafb24677
OH and Charles wrote another option, i don't think we ever tested it.. https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/ti-linux-4.9.y/patches/drivers/ti/gpio/0008-bone-pinmux-helper-Add-support-for-mode-device-tree-.patch P1_02_pinmux { mode = "gpio_pd"; }; Regards, -- Robert Nelson https://rcn-ee.com/ -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
