22 Dec, 2010
1 commit
-
Add OPP data for OMAP34xx and OMAP36xx and initialization functions
to populate OPP tables based on current SoC.
introduce an OMAP generic opp initialization routine which OMAP3
and OMAP4+ SoCs can use to register their OPP definitions.Cc: Thomas Petazzoni
Signed-off-by: Kevin Hilman
Signed-off-by: Nishanth Menon
Signed-off-by: Kevin Hilman
10 Nov, 2010
1 commit
-
The DSS documentation didn't mention the option to give the VRAM start
address.Signed-off-by: Tomi Valkeinen
Signed-off-by: Paul Mundt
09 Dec, 2009
1 commit
-
Signed-off-by: Tomi Valkeinen
04 Sep, 2009
1 commit
-
The interface provides device drivers, CPUFreq, and DSPBridge with a
means of controlling OMAP power management parameters that are not yet
supported by the Linux PM PMQoS interface. Copious documentation is
in the patch in Documentation/arm/OMAP/omap_pm and the interface
header file, arch/arm/plat-omap/include/mach/omap-pm.h.Thanks to Rajendra Nayak for adding CORE (VDD2) OPP
support and moving the OPP table initialization earlier in the event
that the clock code needs them. Thanks to Tero Kristo
for fixing the parameter check in
omap_pm_set_min_bus_tput(). Jouni signed off on Tero's patch.Signed-off-by: Paul Walmsley
Signed-off-by: Kevin Hilman
Signed-off-by: Rajendra Nayak
Signed-off-by: Tero Kristo
Signed-off-by: Jouni Högander
Cc: Tony Lindgren
Cc: Igor Stoppa
Cc: Richard Woodruff
Cc: Anand Sawant
Cc: Sakari Poussa
Cc: Veeramanikandan Raju
Cc: Karthik Dasu