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? Josh [1] https://github.com/RobertCNelson/linux-stable-rcn-ee/blob/29723a20cdfe75e81e964739284643ab32a38231/arch/arm/boot/dts/am335x-bone-crypto-00a0.dtsi -- 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.
