On Tue, Sep 16, 2014 at 4:55 PM, Joshua Datko <[email protected]> wrote: > > > Jason Kridner <jkridner-hcmAuCOw+vXj4SYmN/[email protected]> writes: > > >>> https://github.com/cdsteinkuehler/beaglebone-universal-io/commit/e742ff15f7abbc2cf80141ea49269eb0a2f2a8b3 >> >> Approach looks good to me. I know the dropping of the pin assignment >> in the i2c device tree itself will cause some heartache for some. >> >> I don't see where you removed the definition of the i2c pin settings >> themselves. Will not removing those entries cause headaches by someone >> assuming they are used or is it comfortable for them to simply be >> there by reference? I suspect it would only be an issue if a bug was >> found in the setting and someone missed that the real mode was coming >> from the helper. >> > > I've been trying to follow along with these changes and I admit, I > haven't been able to keep up. > > Some questions: > > 1. My Cape DTS does not explicitly call out for i2c2 [1], with this > change does that, and all capes using i2c2, need to be fixed? > > 2. Is the default mode of pins P_19/20, once user space is reached, GPIO > or i2c2?
Hi Josh, I'm going to make sure we do it both ways. The default "am335x-boneblack.dtb" (<device.dtb>) will have every peripheral enabled and it'll be up to Charles's userspace tool (and a cape database file that we need to write, (it'll probably be bone-script)) to correctly setup the pinmux's for your cape. But i'll also have a backup: <device>-<cape>.dtb, that'll just be the minimal needed for your cape. Which the end user could enable "other" stuff just like in this base dts: https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-bone-crypto-00a0.dts One of the big unknowns i have... How will the "fat" am335x-boneblack.dtb compare with a <device>-<cape>.dtb power wise. Switching i2c/spi/usart/gpio worked well with the 3.8 cape-universal. The big one is getting the hdmi/drm stack to seamlessly work with this setup. 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
