Kevin, On Thu, May 26, 2011 at 12:15, Kevin Hilman <khilman@xxxxxx> wrote: > "Varadarajan, Charulatha" <charu@xxxxxx> writes: > >> On Thu, May 26, 2011 at 03:04, Kevin Hilman <khilman@xxxxxx> wrote: >>> Tarun Kanti DebBarma <tarun.kanti@xxxxxx> writes: >>> >>>> From: Charulatha V <charu@xxxxxx> >>>> >>>> Non-wakeup GPIOs are available only in OMAP2420 and OMAP3430. But >>>> the GPIO driver initializes the non-wakeup GPIO bits for OMAP24xx >>>> (bothe OMAP 2420 and 2430) & not for OMAP3 which is incorrect. >>> >>> Can you cite the documentation you're using for the OMAP3 non-wakeup >>> GPIOs? >> >> I am referring to Table 25-5. GPIO Channel Description at page no 3354 >> OMAP3430 public TRM Version P. >> > > Based on how I understand that, those non-wakeup GPIOs are non-wakeup > because they're not actually mapped anywhere, and not available on > external pins. Therefore, they should not need any special case > handling for this triggering workaround. Okay. Thanks for clarifying. I will not do this for OMAP3. The special case would be only for OMAP2420 against the current code which is handling for OMAP24xx. -V Charulatha > > Kevin > > -- 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
