On Wed, Apr 17, 2013 at 3:52 PM, Jon Hunter <jon-hunter@xxxxxx> wrote: > > On 04/17/2013 08:42 AM, Javier Martinez Canillas wrote: >> On Wed, Apr 17, 2013 at 3:25 PM, Jon Hunter <jon-hunter@xxxxxx> wrote: >>> >>> On 04/17/2013 02:55 AM, Javier Martinez Canillas wrote: >>> >>> ... >>> >>>> There are so many patches flying around in this thread that I missed it :-) >>>> >>>> Sorry about that... >>> >>> No problem. >>> >>>>> I was trying to see if we could find a common solution that everyone >>>>> could use as it seems that ideally we should all be requesting the gpio. >>>>> >>>>> Cheers >>>>> Jon >>>>> >>>>> [1] http://marc.info/?l=linux-arm-kernel&m=136606204823845&w=1 >>>> >>>> btw, I shared the latest patch with only build testing it, but today I >>>> gave a try and I found a problem with this approach. The .xlate >>>> function is being called twice for each GPIO-IRQ so the first time >>>> gpio_request_one() succeeds but the second time it fails returning >>>> -EBUSY. >>> >>> I tried it and I did not see that. I don't see the below warning either. >>> >> >> weird, I wonder what's different here. > > I am testing on an omap4-sdp which uses a spi based ethernet device. > However, I could try with the omap3430-sdp which uses gpmc. > > Cheers > Jon Hi Jon, I just created a new branch using your omap-daily-testing as a base and cherry-picked all the required patches and the .xlate function is working correctly. I don't see the WARN anymore neither is called twice. Sorry for the noise.. Best regards, Javier -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
