Charles, Also, I've been meaning to ask you what you'd think of individual pin overlay files based on universal-IO. I have all of P8 done, or most of( I don't wont touch the eMMC pins - but HDMI + audio is fair game).
I got bored, when our internet bouncing equipment got struck by lightning again this year, and we were without internet for several days again . . . william@eee-pc:~$ ls share/dtb-single/ template-dts.dts univ-P8_11-00A0.dts univ-P8_16-00A0.dts univ-P8_27-00A0.dts univ-P8_32-00A0.dts univ-P8_37-00A0.dts univ-P8_07-00A0.dts univ-P8_12-00A0.dts univ-P8_17-00A0.dts univ-P8_28-00A0.dts univ-P8_33-00A0.dts univ-P8_38-00A0.dts univ-P8_08-00A0.dts univ-P8_13-00A0.dts univ-P8_18-00A0.dts univ-P8_29-00A0.dts univ-P8_34-00A0.dts univ-P8_39-00A0.dts univ-P8_09-00A0.dts univ-P8_14-00A0.dts univ-P8_19-00A0.dts univ-P8_30-00A0.dts univ-P8_35-00A0.dts univ-P8_40-00A0.dts univ-P8_10-00A0.dts univ-P8_15-00A0.dts univ-P8_26-00A0.dts univ-P8_31-00A0.dts univ-P8_36-00A0.dts Was considering how one might implement peripherals into the mix. But I think it should be possible to create individual peripheral overlays, and then just add those in addition to needed pins ? I have not looked too deeply into that yet. On Thu, Jul 28, 2016 at 12:45 AM, William Hermans <[email protected]> wrote: > Thanks Charles. Read this last night, and been meaning to thank you for > the information. But kept getting sidetracked . .. gpio-of-helper, I have > not been able to find decent documentation on that, but I have not looked > recently. Probably somewhere in linux/documentation/ . . . > > On Wed, Jul 27, 2016 at 6:00 AM, Charles Steinkuehler < > [email protected]> wrote: > >> On 7/27/2016 12:33 AM, William Hermans wrote: >> > Charles, >> > >> > Is there a way through modifying your overlay files to put an output >> pin in a >> > specific state as the overlay file is loaded ? I noticed one can change >> input to >> > output as needed in fragment@2. But do not see a way to change pin >> state. unless >> > if it'll work if i replace "input" with hi, or low ? I've replaced with >> "output" >> > and that works . . . e.g. >> > >> > P8_07 { >> > gpio-name = "P8_07"; >> > gpio = <&gpio2 2 0>; >> > dir-changeable; >> > }; >> >> The pin exporting is done by the gpio-of-helper kernel module, so you >> can use anything that driver understands, like init-high or init-low: >> >> P8_07 { >> gpio-name = "P8_07"; >> gpio = <&gpio2 2 0>; >> output; >> init-high; >> }; >> >> -- >> Charles Steinkuehler >> [email protected] >> >> -- >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/27596900-6b9a-88fb-25b3-79427dd4758d%40steinkuehler.net >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORqUTWtnm_Wfh1EFufAoOEQhtqMWSy0m4%3D6YJptwy1jnuA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
