On Mon, Feb 21, 2011 at 12:25:01PM +0530, ext Manuel, Lesly Arackal wrote: > Hi Jean, > > On Fri, Feb 18, 2011 at 10:57 PM, Jean Pihet <jean.pihet@xxxxxxxxxxxxxx> wrote: > > On Fri, Feb 18, 2011 at 6:08 PM, Lesly A M <leslyam@xxxxxx> wrote: > >> Patch series for TWL4030 power scripts and workaround for TWL errata 27. > >> > >> Changes for implementing TWL4030 power scripts recommended by hardware team. > >> Introduced a new TWL4030 power script file, which can be used by different > >> OMAP3 board with the power companion chip TWL4030. > >> > >> Updated the changes for TWL4030 errata 27 & 28, modified the > >> TWL4030 power script and voltage controller setuptime. > >> Workaround for TWL4030 errata 27 & 28 is required for > >> Si version less than or equal to TWL5030 ES1.1. > >> > >> TWL4030 script changes rebased on Kevin's PM tree in pm branch. > >> > >> Changes in v7: > >> changes to fix Nishanth Menon's comments > >> i) Added the TWL4030 Errata 27 fix > >> > >> split the first patch in v6 > >> i) fix for twl4030 script load > >> ii) correct the warning print during script loading > >> > >> Added new patch files > >> i) pmic_info struct cleanup > >> ii) changing sys_off signal polarity > >> > >> Updated the change logs > >> > >> This changes are tested on OMAP3430 & OMAP3630 SDP with off mode enabled in suspend path. > >> Tested with suspend/resume script, which will test system suspend in a loop. > >> Tested for more than 1000 iterations. > > > > Good to see the TWL scripts back in the mainline kernel! > > Are the scripts compatible with the OMAP3 Beagleboard? I would like to > > test the changes on that board. > > I have not tested on Beagleboard. > I think Beagleboard is using different PM IC TPSxxxx. > If its equivalent to TRITON then this script should work on it. As far as I know they are equivalent. I don't know if the errata need to be applied though. Maybe someone from TI can comment? Cheers, Peter. -- 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
