> > *I thought this had no actual bearing on the configuration of things, but > was just there to warn you if any other overlay also claimed those same > strings (e.g. claiming "p9-31" is not the same as "p9.31").*
I'm not a device tree expert. But it does make sense to me that the PIN connected to the AIN7 channel of the ADC module should be explicit. Whatever the case, I noticed the same behavior as Nikos. When attempting to use AIN7 through sysfs, the system complains loudly - Something to the effect that the device is busy, or some such related error. On Mon, Oct 12, 2015 at 4:50 PM, Rick Mann <[email protected]> wrote: > > > On Oct 12, 2015, at 16:28 , William Hermans <[email protected]> wrote: > > > > First: exclusive-use = "P9.31", "P9.40", "P9.37", "P9.38", "P9.33", > "P9.36", "P9.35", "tscadc"; P9.32 seems to be missing. It is my assumption > if you replace "tscadc" with "P9.32" that should fix one configuration > piece for your purposes. > > I thought this had no actual bearing on the configuration of things, but > was just there to warn you if any other overlay also claimed those same > strings (e.g. claiming "p9-31" is not the same as "p9.31"). > > -- > Rick Mann > [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]. > 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]. For more options, visit https://groups.google.com/d/optout.
