[PM-OPP][PATCH 0/2] OMAP: pm: opp: few additional cleanups

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Cleanup opp layer on pending topics:
SRF is dead, so remove the opp_id concept from opp layer, no more
deprecated functions for us.. (series is based on khilman's pm branch)

There are two things pending with opp layer as pointed in the discussion
with Sanjeev:
a) we need to make the opp data definition a little more CPUFREQ independent
 - i have taken this up in patch 2/2
b) The thing pending: how do we fit in mpurate?
Problem that Sanjeev pointed out in the thread[1] was this:
lets say a bootloader running at freq x, runs kernel at freq y, should'nt the
kernel verify if this is a valid freq for that board before setting it?	
	The call sequence currently is:
	(1) arch/arm/plat-omap/clock.c omap_clk_setup
	(2) arch/arm/mach-omap2/clock.c omap2_clk_switch_mpurate_at_boot
	(3) arch/arm/mach-omap2/opp3xxx_data.c omap3_pm_init_opp_table
mpurate is populated at (1), used at (2) and the opp table against which
it can be verified is at (3). here in lies the chicken-or-egg problem :(.
since the operating frequencies are decided based on board behavior as well,
we cant really set the frequency at (2) as we do now, and we may want to
consider the option of moving it down beyond (3).

Note: we will also have to consider the fact that we may need a higher/different
voltage for that mpu frequency as well.. which may mean this handling be
moved out of the clock.c to pm.c instead..

Does anyone have a suggestion as to how we'd want to proceed?
	
Nishanth Menon (2):
  omap: pm: opp: remove opp_id
  omap3: opp: make independent of cpufreq

 arch/arm/mach-omap2/Makefile                       |    5 +--
 .../mach-omap2/{cpufreq34xx.c => opp3xxx_data.c}   |    0
 arch/arm/plat-omap/include/plat/opp.h              |   15 ------
 arch/arm/plat-omap/opp.c                           |   47 --------------------
 4 files changed, 1 insertions(+), 66 deletions(-)
 rename arch/arm/mach-omap2/{cpufreq34xx.c => opp3xxx_data.c} (100%)


Cc: Eduardo Valentin <eduardo.valentin@xxxxxxxxx>
Cc: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx>
Cc: Paul Walmsley <paul@xxxxxxxxx>
Cc: Rajendra Nayak <rnayak@xxxxxx>
Cc: Sanjeev Premi <premi@xxxxxx>
Cc: Thara Gopinath <thara@xxxxxx>
Cc: Tony Lindgren <tony@xxxxxxxxxxx>

Regards,
Nishanth Menon
Ref:
[1]: http://marc.info/?t=127495972700003&r=1&w=2
--
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


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux