Re: [PATCH 00/16] OMAP3: PM: Smartreflex and voltage revamp.

Kevin Hilman
2010-03-06T01:05:49Z

Thara Gopinath <thara@ti.com> writes:

> From: Thara Gopinath <thara@omaplbp.(none)>
>
> This main motivations behind this patch series are the following
> 1. Making smartreflex a platform driver with omap-device layer.
> 2. Separating voltage specific code from smartreflex.c and other
> locations and consolidating them into voltage.c and voltage.h.
> 3. Smartreflex module can have Class 3 or Class 2 implementations
> depending on the PMIC in use. Making smartreflex.c capable
> of handling both the class implementaions and separating out
> class specific code into a separate class driver.
> 4. Implementating latest TI recommended register settings for
> Smartreflex and Voltage processor module as well as recommended
> sequences for enabling and disabling of Smartreflex and Voltage
> processor modules.
> 5. Implementing VP force update method of voltage scaling which is
> again TI hardware recommended.
>
> What this patch series does not address are
> 1. Separating PMIC specific portions from smartreflex and voltage code.
> 2. OMAP3630 and OMP4 smartreflex support.
>
> This patch series is based on Kevin's PM tree origin/pm-wip-opp branch
> and is dependent on the following patches not yet applied onto this branch.

Hi Thara,

One other request for V2.

Could you separate out any patches to SRF (resourc34xx) into their own
patches please? This will facilitate upstream merging when SR is
finalized because while SR will be (hopefully) going upstream soon,
SRF will not.

A quick look shows patches 5, 8, 9 as having changes to
resource*.[ch]. Please separate those out as separate patches.

Once again, thanks for your efforts on this much needed SR rework,

Kevin