Charles, The idea I had in my mind is that someone could potentially, more easily. Figure out how to use device tree files. By examining something that is closer to self explanatory, and not a wall of code to hurdle. I think your overlays illustrate very well how device tree files work, but that wall of code obstacle makes it much harder to read through. This way, you can see what exactly is needed for a single pin, and by extension should be able to make it much easier for a beginner to combine pins into their own overlay file. That's how it worked for me anyway. I understand device tree source files, pin muxing, and all this much better. Granted, I still do not know *everything*, but that's ok. I feel really good about how much I understand right now.
Also, as I mentioned above. I needed a way to mux pins for my Bonejs project, and I think this is the perfect, and most "generic" way of fitting all needs, for any potential users of Bonejs. But, I am still open to other ideas / options. On Thu, Jul 28, 2016 at 5:07 AM, Charles Steinkuehler < char...@steinkuehler.net> wrote: > On 7/28/2016 2:52 AM, William Hermans wrote: > > 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). > <snip> > > 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. > > An "exploded" universal overly should work fine. The basic idea > remains to allow pin-muxing in user-space, but breaking out the > peripherals individually would allow lower power operation by only > loading what's necessary. I'm not sure how much benefit there is to > breaking out each pin individually, but there shouldn't be any harm > (besides having to load a lot more overlays to get something done). > > -- > Charles Steinkuehler > char...@steinkuehler.net > > -- > 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/6b589e72-2518-5be1-76b9-acd3312bb5f8%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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORpSkaymwQZox23Fz2EdQZa9zXrpVmVLo%2BG-wYpyaU7CMA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
