On Tue, Jan 05, 2016 at 10:54:25AM -0500, Tom Rini wrote: > On Tue, Jan 05, 2016 at 10:47:41AM +0000, Jason Kridner wrote: > > > Tom, > > > > I just ran into the below old issue with the 'gpio' command on the u-boot > > mainline (returning -22 on 'gpio set 53'). Was commit > > 0a9e34056fcf86fb64e70bd281875eb7bbdbabde tested on AM335x? > > Oh hell. I did test this at the time and I tested it again this morning > and I see what's going on. When I did my tests I was testing some other > DM related changes and so I had the device tree also included and that's > how all of the GPIOs were found. I probably also tested on an old > beagleboard without a device tree. But I did forget to test am335x > without a device tree and that's where it's failing now. I'm flashing > one of the user LEDs in my office right now and I'll post something to > the mailing lists shortly that also fixes OMAP4/OMAP5.
Well, the good news is that for OMAP4/5 (and DRA7xx and so forth so X15) we don't enable DM_GPIO so they're not broken by this at least. -- Tom -- 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.
