In my reply to this series from Lesly:

  [PATCH v2 0/6] omap3: pm: Update TRITON power scripts and making it generic

I made this proposal:

> Second, your series is making it clear we need some common VC init.
> And this common VC init should be probably be separated from PMIC
> init/setup.  So before we go much further with this, I think it's time
> for some common VC infrastructure.
>
> So here's a proposal off the top of my head:
>
> - create new file(s): vc34xx.c, vc.h (or something like that)
> - move the common prm_setup_times init and structs there
> - move VC init from pm34xx.c (omap3_pm_init_vc, configure_vc, etc.)
>
> We'll then have all the VC init/setup in a single place.  

To help get things moving along in that direction, I created
this series to get things started.

Comments are welcome.

This series applies on to of current PM branch, and is also available
in my tree as the branch 'pm-wip/vc',

Kevin

Kevin Hilman (3):
  OMAP3: VC: create common init code
  OMAP3: VC: simply struct copy in init_vc routine
  OMAP3: VC: 3430SDP: remove prm_setup_vc, done in common VC code

 arch/arm/mach-omap2/Makefile        |    3 +-
 arch/arm/mach-omap2/board-3430sdp.c |   18 ------
 arch/arm/mach-omap2/pm.h            |   25 ---------
 arch/arm/mach-omap2/pm34xx.c        |   91 -------------------------------
 arch/arm/mach-omap2/vc.c            |  102 +++++++++++++++++++++++++++++++++++
 arch/arm/mach-omap2/vc.h            |   47 ++++++++++++++++
 6 files changed, 151 insertions(+), 135 deletions(-)
 create mode 100644 arch/arm/mach-omap2/vc.c
 create mode 100644 arch/arm/mach-omap2/vc.h

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

Reply via email to