Kevin, On Thu, Nov 25, 2010 at 07:10, Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> wrote: > "Varadarajan, Charulatha" <charu@xxxxxx> writes: > >> Implement OMAP GPIO module in platform device model. OMAP2+ specific GPIO >> module uses hwmod FW. >> >> Tested on OMAP2430, OMAP44430, OMAP3430 SDP boards, OMAP4430 Blaze board >> and zoom3 board. Verified that this patch series does not break the OMAP1 >> build. >> >> Version History: >> --------------- >> v7 Series: >> - Use gpio iclks as main_clk in OMAP3 & OMAP4 >> - Implement GPIO as a platform device (use hwmod FW for OMAP2+) >> and the implementation is similar to current GPIO code. Does not >> modify the gpio suspend/ resume/ prepare for odle and resume after >> idle code and these modifications would be done in a separate patch >> series. This was suggested by Kevin in another internal email thread. > > OK, I'm ready to merge this series, and we can deal with the runtime PM > conversion in another series as that's where the tricky part lies. Thanks. > > However, I'd like one more rebase/retest due to some other dependencies. > Can you rebase/retest using my current pm-core branch? Sure I will do that. > That includes > several dependencies that are also targetted for 2.6.38: > > - misc. PM fixes > - i2c hwmod + runtime PM conversion (my pm-hwmod-i2c branch) > - several board file changes/updates (Tony's devel-board branch) > - hwmod core fixes (Paul's hwmod_a_2.6.38 branch) > - wdt hwmod cleanups (Paul's wdt_2.6.38 branch) > > Also, can you collect the acks from Benoît and update your changelogs to > include them. Thanks. Sure. > > Please be sure your board file changes are updated for the board file > changes in the devel-board branch. Okay. But if it is different, should I send only the board files changes on devel-board branch as a separate patch mentioning the dependencies on my patch series? -- 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
