aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2011-06-20arm: omap3: beagle: Ensure msecure is mux'd to be able to set the RTCdvhart/yocto/standard/beagleboardAlexander Holler
commit e2a346a2a054f7 from git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git Without msecure beeing high it isn't possible to set (or start) the RTC. Tested with a BeagleBoard C4. Signed-off-by: Alexander Holler <holler@ahsoftware.de> Signed-off-by: Tony Lindgren <tony@atomide.com> Integrated-by: Lu Jingdong <jingdong.lu@windriver.com>
2011-06-20board-omap3beagle: allow for building without wl1271Darren Hart
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea While the header file wl12xx.h is ifdef'd to include if the wl1271 driver is built, the init routine calls into it regardless. Ideally, the module would perform its own initialization at load time and we wouldn't need to ifdef these calls in the general board initialization. For now, follow the existing practice in this file and ifdef the wl1271 init block. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-06-20board-omap3beagle: whitespace cleanupDarren Hart
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea Eliminate leading and trailing whitespace. Indent with tabs. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-06-20BeagleBoard: Adjust USER button pin for xMKoen Kooi
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
2011-06-20omap3: allow 1GHz mpuratesKoen Kooi
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
2011-06-20xM audio fix from AshokRobert Nelson
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea Signed-off-by: Robert Nelson <robertcnelson@gmail.com>
2011-06-20beagleboard: hack in support from xM rev CKoen Kooi
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
2011-06-20Bluetooth: btwilink driverPavan Savoy
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea -- patch description -- This is the bluetooth protocol driver for the TI WiLink7 chipsets. Texas Instrument's WiLink chipsets combine wireless technologies like BT, FM, GPS and WLAN onto a single chip. This Bluetooth driver works on top of the TI_ST shared transport line discipline driver which also allows other drivers like FM V4L2 and GPS character driver to make use of the same UART interface. Kconfig and Makefile modifications to enable the Bluetooth driver for Texas Instrument's WiLink 7 chipset. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com>
2011-06-20drivers:misc:ti-st: change protocol parse logicPavan Savoy
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea TI shared transport driver had to specifically know the protocol headers for each type of data it can receive to properly re-assemble data if its fragmented during UART transaction or fragment if the data is an assembly of different protocol data. Now the individual protocol drivers provide enough header information for shared transport driver to do this in a generic way applicable for all protocols. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com>
2011-06-20drivers:media:radio: Update Kconfig and Makefile for wl128x FM driver.Manjunatha Halli
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea Signed-off-by: Manjunatha Halli <manjunatha_halli@ti.com> Reviewed-by: Hans Verkuil <hverkuil@xs4all.nl>
2011-06-20drivers:media:radio: wl128x: Kconfig & Makefile for wl128x driverManjunatha Halli
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea Signed-off-by: Manjunatha Halli <manjunatha_halli@ti.com> Reviewed-by: Hans Verkuil <hverkuil@xs4all.nl>
2011-06-20drivers:media:radio: wl128x: FM driver TX sourcesManjunatha Halli
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea This has implementation for FM TX functionality. It communicates with FM V4l2 module and FM common module. Signed-off-by: Manjunatha Halli <manjunatha_halli@ti.com> Reviewed-by: Hans Verkuil <hverkuil@xs4all.nl>
2011-06-20drivers:media:radio: wl128x: FM driver RX sourcesManjunatha Halli
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea This has implementation for FM RX functionality. It communicates with FM V4l2 module and FM common module Signed-off-by: Manjunatha Halli <manjunatha_halli@ti.com> Reviewed-by: Hans Verkuil <hverkuil@xs4all.nl>
2011-06-20drivers:media:radio: wl128x: FM Driver Common sourcesManjunatha Halli
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea These are the sources for the common interfaces required by the FM V4L2 driver for TI WL127x and WL128x chips. These implement the FM channel-8 protocol communication with the chip. This makes use of the Shared Transport as its transport. Signed-off-by: Manjunatha Halli <manjunatha_halli@ti.com> Reviewed-by: Hans Verkuil <hverkuil@xs4all.nl>
2011-06-20drivers:media:radio: wl128x: FM Driver V4L2 sourcesManjunatha Halli
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea This module interfaces V4L2 subsystem and FM common module. It registers itself with V4L2 as Radio module. Signed-off-by: Manjunatha Halli <manjunatha_halli@ti.com> Reviewed-by: Hans Verkuil <hverkuil@xs4all.nl>
2011-06-20drivers:media:radio: wl128x: FM Driver common header fileManjunatha Halli
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea These are common headers used in FM submodules (FM V4L2, FM common, FM Rx,and FM TX). Signed-off-by: Manjunatha Halli <manjunatha_halli@ti.com> Reviewed-by: Hans Verkuil <hverkuil@xs4all.nl>
2011-06-20wl12xx: Unset bssid filter, ssid and bssid from firmware on disassocJuuso Oikarinen
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea On the disassociation event from the mac80211, the wl12xx driver does not clear the chipset configuration related to the AP - i.e. it does not perform a DISCONNECT and then a JOIN with zero SSID and dummy BSSID. Also, it does not unset the BSSID filter. Often this is not a problem, as the above is performed upon entering idle state. But if a scenario arises where a new association is attempted without cycling through idle state, the new association will fail. Fix this by resetting the firmware state on disassociation. Signed-off-by: Juuso Oikarinen <juuso.oikarinen@nokia.com> Reviewed-by: Luciano Coelho <luciano.coelho@nokia.com> Signed-off-by: Luciano Coelho <luciano.coelho@nokia.com>
2011-06-20wl1271: set wl->vif only if add_interface succeeded.Eliad Peller
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea set wl->vif to the newly created interface only after the firmware booted successfully. on the way - make the function flow more clear. Signed-off-by: Eliad Peller <eliad@wizery.com> Reviewed-by: Luciano Coelho <luciano.coelho@nokia.com> Signed-off-by: Luciano Coelho <luciano.coelho@nokia.com>
2011-06-20wl1271: 11n Support, functionality and configuration abilityShahar Levi
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea Add 11n ability in scan, connection and using MCS rates. The configuration is temporary due to the code incomplete and still in testing process. That plans to be remove in the future. Signed-off-by: Shahar Levi <shahar_levi@ti.com> Reviewed-by: Luciano Coelho <luciano.coelho@nokia.com> Signed-off-by: Luciano Coelho <luciano.coelho@nokia.com>
2011-06-20wl1271: 11n Support, ACX CommandsShahar Levi
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea Added ACX command to the FW for 11n support. Signed-off-by: Shahar Levi <shahar_levi@ti.com> Reviewed-by: Luciano Coelho <luciano.coelho@nokia.com> Signed-off-by: Luciano Coelho <luciano.coelho@nokia.com>
2011-06-20wl1271: 11n Support, Add DefinitionsShahar Levi
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea Two acx commands: ht_capabilities & ht_information, 11n sta capabilities macro. Signed-off-by: Shahar Levi <shahar_levi@ti.com> Reviewed-by: Luciano Coelho <luciano.coelho@nokia.com> Signed-off-by: Luciano Coelho <luciano.coelho@nokia.com>
2011-06-20wl12xx: Read MAC address from NVS file on HW startupArik Nemtsov
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea Try to read the MAC address from the on-disk NVS file. A non-zero MAC address is required to add an AP interface. Signed-off-by: Arik Nemtsov <arik@wizery.com> Reviewed-by: Luciano Coelho <coelho@ti.com> Signed-off-by: Luciano Coelho <coelho@ti.com>
2011-06-20OMAP: Enable Magic SysRq on serial console ttyOxThomas Weber
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea Magic SysRq key is not working for OMAP on new serial console ttyOx because SUPPORT_SYSRQ is not defined for omap-serial. This patch defines SUPPORT_SYSRQ in omap-serial and enables handling of Magic SysRq character. Signed-off-by: Thomas Weber <weber@corscience.de>
2011-06-20omap3: Add basic support for 720MHz partSanjeev Premi
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea This patch adds support for new speed enhanced parts with ARM and IVA running at 720MHz and 520MHz respectively. These parts can be probed at run-time by reading PRODID.SKUID[3:0] at 0x4830A20C [1]. This patch specifically does following: * Detect devices capable of 720MHz. * Add new OPP * Ensure that OPP is conditionally enabled. * Check for presence of IVA before attempting to enable the corresponding OPP. [1] http://focus.ti.com/lit/ug/spruff1d/spruff1d.pdf Signed-off-by: Sanjeev Premi <premi@ti.com>
2011-06-20OMAP3: beagle xm: enable upto 1GHz OPPNishanth Menon
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea Beagle XM uses 3730 and the board design allows enabling 800MHz and 1GHz OPPs. tweak the default table to allow for higher OPP tables Reported-by: Koen Kooi <koen@beagleboard.org> Signed-off-by: Nishanth Menon <nm@ti.com>
2011-06-20omap3|4: opp: make omapx_opp_init non-staticNishanth Menon
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea omap3 and omap4 opp_init should be made non-static to allow for platform specific opp table tweaking. making these static conflicts with the definition in pm.h(global) as well. we include pm.h as well to ensure that there are no such prototype conflicts with actual implementation in the future. Signed-off-by: Nishanth Menon <nm@ti.com>
2011-06-20OMAP3: Add voltage dependency table for VDD1.Thara Gopinath
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea In OMAP3, for perfomrance reasons when VDD1 is at voltage above 1.075V, VDD2 should be at 1.15V for perfomrance reasons. This patch introduce this cross VDD dependency for OMAP3 VDD1. Signed-off-by: Thara Gopinath <thara@ti.com>
2011-06-20OMAP3: Introduce voltage domain info in the hwmod structures.Thara Gopinath
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea This patch adds voltage domain info in the relevant device hwmod structures so as to enable OMAP3 DVFS support. Signed-off-by: Thara Gopinath <thara@ti.com>
2011-06-20OMAP3: Update cpufreq driver to use the new set_rate APIThara Gopinath
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea This patch updates the cpufreq driver to use the device set rate API to scale the mpu frequency for OMAP3. Signed-off-by: Thara Gopinath <thara@ti.com>
2011-06-20OMAP3: Introduce custom set rate and get rate APIs for scalable devicesThara Gopinath
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea This patch also introduces omap3_mpu_set_rate, omap3_iva_set_rate, omap3_l3_set_rate, omap3_mpu_get_rate, omap3_iva_get_rate, omap3_l3_get_rate as device specific set rate and get rate APIs for OMAP3 mpu, iva and l3_main devices. This patch also calls into omap_device_populate_rate_fns during system init to register various set_rate and get_rate APIs with the omap device layer Signed-off-by: Thara Gopinath <thara@ti.com>
2011-06-20OMAP: Disable smartreflex across DVFSThara Gopinath
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea This patch disables smartreflex for a particular voltage domain when the the voltage domain and the devices belonging to it is being scaled and re-enables it back once the scaling is done. Signed-off-by: Thara Gopinath <thara@ti.com>
2011-06-20OMAP: Introduce device scaleThara Gopinath
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea This patch adds omap_device_scale API which can be used to generic device rate scaling. Signed-off-by: Thara Gopinath <thara@ti.com>
2011-06-20OMAP: Introduce dependent voltage domain support.Thara Gopinath
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea There could be dependencies between various voltage domains for maintaining system performance or hardware limitation reasons like VDD<X> should be at voltage v1 when VDD<Y> is at voltage v2. This patch introduce dependent vdd information structures in the voltage layer which can be used to populate these dependencies for a voltage domain. This patch also adds support to scale the dependent vdd and the scalable devices belonging to it during the scaling of a main vdd through omap_voltage_scale. Signed-off-by: Thara Gopinath <thara@ti.com>
2011-06-20OMAP: Voltage layer changes to support DVFS.Thara Gopinath
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea This patch introduces an API to take in the voltage domain and the new voltage as parameter and to scale all the scalable devices associated with the the voltage domain to the rate corresponding to the new voltage and scale the voltage domain to the new voltage. Signed-off-by: Thara Gopinath <thara@ti.com>
2011-06-20OMAP: Introduce device specific set rate and get rate in omap_device structureThara Gopinath
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea This patch extends the omap_device structure to contain pointers to scale the operating rate of the device and to retrieve the operating rate of the device. This patch also adds the three new APIs in the omap device layer namely omap_device_set_rate that can be called to set a new operating rate for a device, omap_device_get_rate that can be called to retrieve the operating frequency for a device and omap_device_populate_rate_fns to populte the device specific set_rate and get_rate API's. The omap_device_set_rate and omap_device_get_rate does some routine error checks and finally calls into the device specific set_rate and get_rate APIs populated through omap_device_populate_rate_fns. Signed-off-by: Thara Gopinath <thara@ti.com>
2011-06-20OMAP: Introduce API to register a device with a voltagedomainThara Gopinath
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea This patch adds an API in the voltage layer that can be used during omap_device_build to register the built device with the voltage domain. This API is to be typically called only once per device during the device registeration. This approach makes it easy during dvfs to scale all the devices associated with a voltage domain and then scale the voltage domain. Signed-off-by: Thara Gopinath <thara@ti.com>
2011-06-20OMAP: Introduce API in the OPP layer to find the opp entry corresponding to ↵Thara Gopinath
a voltage. Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea This patch adds an API in the opp layer to get the opp table entry corresponding to the voltage passed as the parameter. Signed-off-by: Thara Gopinath <thara@ti.com>
2011-06-20OMAP: Introduce a user list for each voltage domain instance in the voltage ↵Thara Gopinath
driver. Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea This patch introduces a user list of devices associated with each voltage domain instance. The user list is implemented using plist structure with priority node populated with the voltage values. This patch also adds an API which will take in a device and requested voltage as parameters, adds the info to the user list and returns back the maximum voltage requested by all the user devices. This can be used anytime to get the voltage that the voltage domain instance can be transitioned into. Signed-off-by: Thara Gopinath <thara@ti.com>
2011-06-20OMAP: PM: CPUFREQ: Fix conditional compilationSilesh C V
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea Fix conditional compilation. A conditional expresiion should follow "#elif", in this case #elif clause should check whether CONFIG_ARCH_OMAP3 is defined or not (ie. defined(CONFIG_ARCH_OMAP3)) rather than checking for the value of the macro. Signed-off-by: Silesh C V <silesh@ti.com>
2011-06-20OMAP3 PM: CPUFreq driver for OMAP3Rajendra Nayak
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea CPUFreq driver for OMAP3 With additional fixes and cleanups from Tero Kristo: - Fix rate calculation bug in omap3_select_table_rate - Refreshed DVFS VDD1 control against latest clock fw Signed-off-by: Tero Kristo <tero.kristo@nokia.com> Signed-off-by: Rajendra Nayak <rnayak@ti.com> OMAP3: PM: CPUFreq: Fix omap_getspeed. Signed-off-by: Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com> Make sure omap cpufreq driver initializes after cpufreq framework and governors Signed-off-by: Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com> merge: CPUFreq: remove obsolete funcs OMAP3 clock: Update cpufreq driver This patch removes all refrences to virtual clock nodes in CPUFreq driver. Signed-off-by: Rajendra Nayak <rnayak@ti.com> Signed-off-by: Tero Kristo <tero.kristo@nokia.com> Signed-off-by: Jean Pihet <jpihet@mvista.com> PM: Prevent direct cpufreq scaling during initialization It is seen that the OMAP specific cpufreq initialization code tries to scale the MPU frequency to the highest possible without taking care of the voltage level. On power on reset the power IC does not provide the necessary voltage for the highest available MPU frequency (that would satisfy all Si families). This potentially is an window of opportunity for things to go wrong. Signed-off-by: Romit Dasgupta <romit@ti.com> Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com> OMAP3: PM: enable 600MHz (overdrive) OPP Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com> omap3: introduce cpufreq OMAP OPP layer functions now have dependencies of CONFIG_CPU_FREQ only. With this patch, omap opp layer now has its compilation flags bound to CONFIG_CPU_FREQ. Also its code has been removed from pm34xx.c. A new file has been created to contain cpu freq code related to OMAP3: cpufreq34xx.c OMAP34xx and OMAP36xx family OPPs are made available Signed-off-by: Eduardo Valentin <eduardo.valentin@nokia.com> Signed-off-by: Paul Walmsley <paul@pwsan.com> Signed-off-by: Nishanth Menon <nm@ti.com> Signed-off-by: Vishwanath BS <vishwanath.bs@ti.com> Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com> Signed-off-by: Romit Dasgupta <romit@ti.com> Signed-off-by: Rajendra Nayak <rnayak@ti.com> omap3: cpufreq: allow default opp table init For board files which choose to override the defaults, the existing mechanism will work, for boards that would like to work with defaults, allow init_common_hw to call init_opp_table to initialize if not already initialized. this will allow all omap boards which have opp tables predefined for a silicon to use the same. Originally reported for overo: http://marc.info/?t=127265269400004&r=1&w=2 Signed-off-by: Nishanth Menon <nm@ti.com> Reported-by: Peter Tseng <tsenpet09@gmail.com> Cc: Cliff Brake <cliff.brake@gmail.com> Cc: Kevin Hilman <khilman@deeprootsystems.com> OMAP2: update OPP data to be device based Cc: Nishanth Menon <nm@ti.com> Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com> OMAP3: CPUfreq: update to device-based OPP API Update usage of OPP API to use new device-based API. This requires getting the 'struct device' for the MPU and using that with the OPP API. Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com> omap3: opp: make independent of cpufreq Make opp3xx data which is registered with the opp layer dependent purely on CONFIG_PM as opp layer and pm.c users are CONFIG_PM dependent not cpufreq dependent. so we rename the data definition to opp3xxx_data.c (inline with what we have for omap2), also move the build definition to be under the existing CONFIG_PM build instead of CPUFREQ. Cc: Eduardo Valentin <eduardo.valentin@nokia.com> Cc: Kevin Hilman <khilman@deeprootsystems.com> Cc: Paul Walmsley <paul@pwsan.com> Cc: Rajendra Nayak <rnayak@ti.com> Cc: Sanjeev Premi <premi@ti.com> Cc: Thara Gopinath <thara@ti.com> Cc: Tony Lindgren <tony@atomide.com> Signed-off-by: Nishanth Menon <nm@ti.com>
2011-06-20OMAP: CPUfreq: ensure policy is fully initializedKevin Hilman
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea Ensure policy min/max/cur values are initialized when OMAP CPUfreq driver starts. Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
2011-06-20OMAP: CPUfreq: ensure driver initializes after cpufreq framework and governorsPeter 'p2' De Schrijver
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea Signed-off-by: Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com> Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
2011-06-20OMAP3: PM: Adding T2 enabling of smartreflexThara Gopinath
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea The smartreflex bit on twl4030 needs to be enabled by default irrespective of whether smartreflex module is enabled on the OMAP side or not. This is because without this bit enabled the voltage scaling through vp forceupdate does not function properly on OMAP3. Signed-off-by: Thara Gopinath <thara@ti.com>
2011-06-20OMAP: DSS2: Add DSS2 support for OveroSteve Sakoman
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea
2011-06-20OMAP: DSS2: check for both cpu type and revision, rather than just revisionSteve Sakoman
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea
2011-06-20ARM: OMAP: automatically set musb mode in platform data based on CONFIG optionsSteve Sakoman
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea
2011-06-20RTC: add support for backup battery rechargeSteve Sakoman
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea
2011-06-20ARM: OMAP2: mmc-twl4030: move clock input selection prior to vcc testSteve Sakoman
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea otherwise it is not executed on systems that use non-twl regulators
2011-06-20OMAP: DSS2: add bootarg for selecting svideo or composite for tv outputSteve Sakoman
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea also add pal-16 and ntsc-16 omapfb.mode settings for 16bpp
2011-06-20OMAP: DSS2: Add support for LG Philips LB035Q02 panelSteve Sakoman
Taken from http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap ea3b39eb7f559c5678e862c58784fedb67d139ea