Skip to content

OMAP: Adding Smartreflex and Voltage driver support

Kevin Hilman linux-arm-kernel linux-omap 2 versions New

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v6 Latest posting 2/22 of 10 patches 0 repliesNew
  2. v6 posting 1/20 of 10 patches 0 repliesSuperseded

2 of 10 patches are in this archive. The cover letter announces 10.

Patches in v6 posting 2/2 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/10OMAP3: PM: Adding voltage driver support.arch/arm/mach-omap2/Makefile+1 -10 replies
7/10OMAP3: PM: Adding T2 enabling of smartreflex support+0 -02 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v6 yet.

Read the v6 thread

Cover letter [PATCH v6 00/10] OMAP: Adding Smartreflex and Voltage driver support
Quoted 9 lines · Tony Lindgren
Quoted 8 lines · Kevin Hilman
Quoted 3 lines · Thara Gopinath

This patch series introduces smartreflex and voltage driver support for OMAP3430 and OMAP3630. SmartReflex modules do adaptive voltage control for real-time voltage adjustments.

Thanks Thara, these are looking good for 2.6.38.

Quoted 7 lines
Quoted 2 lines

Tony, unless there are major objections, I'll be queuing these two SR series for 2.6.38. They have dependencies on Paul's integration branch

Well looking at patch 3/6 I think it should live under drivers somewhere and mostly be compiled as a module. Probably the only change needed for that is to not call cpu_is_omapxxxx but instead use some flags passed in the platform_data. Otherwise the whole series looks OK to me.

Moving this to be a regulator driver is part of the medium-term plan, and is already under development. For this phase, we just split up the current driver into device and driver code and left under mach-omap2. We are investigating (and making) changes to the regulator core so that SmartReflex can be converted into a real regulator driver, but that is still under development.

So, in the mean time, I'd like to merge this version so that other development that depends on this (the regulator work mentioned above, the DVFS work, etc.) can have a stable starting point.

Kevin