Lesly A M <[email protected]> writes:

> 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, and modified the
> TWL4030 power script.
> 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.

This doesn't apply to the current PM branch.  I dropped the old scripts
from the PM branch some time back.  It should be a simple rebase, and
only affects PATCH 6/8.  After the rebase, it will only add the new
stuff to the 3430SDP board file instead of also delete the old scripts.

Also, minor nit: please consistenly capitlize acronyms: API, OMAP, etc,
and the singular for errata is erattum.  This affects subjects,
changelogs comments etc.

> 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) changing sys_off signal polarity
>
> Changes in v8:
>       updated the change logs
>       moving the TWL IDCODE checking to twl-core.c
>
> Since the voltage layer is evolving to a new design, the voltage dependant
> changes required for the TRITON script are not incorporated in the patch 
> series.
> So this TRITON script patch series can be tested with a separate patch for
> voltage layer changes.
>
>       lnk: http://pastebin.mozilla.org/1118306

I'm OK with leaving the voltage layer changes for a separate series, but
in order to test this should also be rebased against my current PM branch.

For future reference, my pm-core branch includes only patches/series
that are already queued for upstream, or will be queued for the next
merge window.

Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to