summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2012-07-10UBUNTU: enable HDMI audioXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10UBUNTU: v4l2 alignmentXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10UBUNTU: enbale TFP410Xavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10UBUNTU: disable MFD_OMAP_CONTROLGuillaume Aubertin
2012-07-10UBUNTU: Config enable WLCOREXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10UBUNTU: Config enable RPC_OMAPXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10UBUNTU: Config enable OMAP_RPMSG_RESMGRXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10UBUNTU: Config disable CPU_FREQ_GOV_INTERACTIVEXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10UBUNTU: Config updateXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10UBUNTU: Config: set cpu-freq governors as staticSebastien Jan
Signed-off-by: Sebastien Jan <s-jan@ti.com>
2012-07-10UBUNTU: Config RPMSGXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10UBUNTU: Config disable CPU_IDLEXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10UBUNTU: config add SCM and TEMP_SENSORXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10UBUNTU: config add STMXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10UBUNTU: Disable LIS3L02DQXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10UBUNTU: Disable SENSORS_AK8975Xavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10UBUNTU: Disable EZX_PCAPXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10UBUNTU: disable EETI touchscreenXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10UBUNTU: Config updateXavier Boudet
* K3.4 * Enable RPMSG * Enable VIRTIO * Config update vs 3.3.0-1482.3 Signed-off-by: Xavier Boudet <x-boudet@ti.com> Config updates Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10UBUNTU: exclude crypto-modules and sata-modules from udebXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10UBUNTU: SAUCE: [arm] fixup __aeabi_uldivmod undefined build errorLeann Ogasawara
When building on arm we run into the following build error due to gcc-4.6 optimizing do_div into a uldivmod call: ERROR: "__aeabi_uldivmod" [drivers/scsi/megaraid/megaraid_sas.ko] undefined! Inline some assembly to prevent the compiler optimization. Signed-off-by: Leann Ogasawara <leann.ogasawara@canonical.com>
2012-07-10UBUNTU: add omap_drv.h and omap_drm.h to linux-headers-<abi>-omap4Xavier Boudet
Add sym link for omap_drm.h and omap_drv.h in include/linux Force delivery of the 2 files into drivers/staging/omapdrm Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10LINARO: Use KBUILD_SCRIPTROOT to cross build scriptsXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10KBuild: Allow scripts/* to be cross compiledJohn Rigby
Cross compiling the binaries in scripts/* is not possible because various makefiles assume that $(obj)/whatever is executable on the build host. This patch introduces a new variable called KBUILD_SCRIPTROOT that points to script/binaries to use while cross compiling. Usage: Build scripts for the build host: make O=path/to/buildhost/buildscripts \ silentoldconfig prepare scripts Then cross build script for target: make O=path/to/target/buildscripts \ HOSTCC=$CROSS_COMPILE \ KBUILD_SCRIPTROOT=path/to/buildhost/buildscripts silentoldconfig prepare scripts This patch does not use KBUILD_SCRIPTROOT for all script invocations it only redefines the following if KBUILD_SCRIPTROOT is defined. scripts/Makefile.build scripts/basic/fixdep --> $(KBUILD_SCRIPTROOT)/scripts/basic/fixdep scripts/kconfig/Makefile $(obj)/conf --> $(KBUILD_SCRIPTROOT)/scripts/kconfig/conf scripts/mod/Makefile $(obj)mk_elfconfig --> $(KBUILD_SCRIPTROOT)/scripts/mod/mk_elfconfig Signed-off-by: John Rigby <john.rigby@linaro.org>
2012-07-10UBUNTU: Initial DebianizationXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10Revert "ASoC: dapm: Remove SND_SOC_DAPM_MICBIAS_E()"Xavier Boudet
This reverts commit 5fc9aced13ae4bca67408816908be75684c1e7ba.
2012-07-10UBUNTU: add include guards to iomap.hXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10HACK: drm_gem_mmap - do not check valid sizeXavier Boudet
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
2012-07-10fix ref leak of external buffers (merge back to plugin API)Rob Clark
drm_gem_mmap() increments the ref count, and expects the corresponding vm_close fxn to decrement it.. otherwise you have a memory leak.
2012-07-10omapdce: workaround for a codec bug in vc1vdec and mpeg2vdecAlessandro Decina
vc1vdec and mpeg2vdec want XDM_MEMTYPE_RAW instead of XDM_MEMTYPE_TILEDPAGE as the memType for outbufs.
2012-07-10mfd: omap: control: usb-phy: introduce the ctrl-module usb driverEduardo Valentin
Created a new platform driver for the platform device created by the control module mfd core, wrt usb. This driver has API's to power on/off the phy and the API's to write to musb mailbox. (p.s. the mailbox for musb in omap4 is present in system control module) Change-Id: I3260e7e9b2091b75620b85ede5b2a09d097a9b37 [kishon@ti.com: wrote the original API's related to USB functions] Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com> Signed-off-by: Eduardo Valentin <eduardo.valentin@ti.com> Signed-off-by: Radhesh Fadnis <radhesh.fadnis@ti.com>
2012-07-10mfd: omap: control: core system control driverEduardo Valentin
This patch introduces a MFD core device driver for OMAP system control module. The control module allows software control of various static modes supported by the device. It is composed of two control submodules: general control module and device (padconfiguration) control module. In this patch, the children defined are for: . USB-phy pin control . Bangap temperature sensor Device driver is probed with postcore_initcall. However, as some of the APIs exposed by this driver may be needed in very early init phase, an early init class is also available: "early_omap_control". Change-Id: I0e5a62508dbdfe0a677c9d833cf52474cd8b625e Signed-off-by: J Keerthy <j-keerthy@ti.com> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com> Signed-off-by: Eduardo Valentin <eduardo.valentin@ti.com> Signed-off-by: Radhesh Fadnis <radhesh.fadnis@ti.com>
2012-07-10omapdce: synchronize with GPURob Clark
If a buffer is passed in which is still being read by the GPU, wait for it to become writable. If userspace takes care not to pass in an in-use buffer, this will have no effect, but if userspace does not know to synchronize with the GPU this will prevent rendering artifacts resulting from writing a future frame into a buffer the GPU is still reading. Signed-off-by: Rob Clark <rob@ti.com>
2012-07-10omapdce: simplify the logic a bitRob Clark
Signed-off-by: Rob Clark <rob@ti.com>
2012-07-10Blaze: register regulators to resource managerHervé Fache
Signed-off-by: Hervé Fache <h-fache@ti.com>
2012-07-10Blaze: add cam2pwr regulatorHervé Fache
Signed-off-by: Hervé Fache <h-fache@ti.com>
2012-07-10omap: clock: export symbol 'omap_clk_get_by_name'Hervé Fache
Signed-off-by: Hervé Fache <h-fache@ti.com>
2012-07-10ARM: OMAP2+: omap_hwmod: Add api to enable/disable module level wakeup eventsGovindraj.R
On 24xx/34xx/36xx Module level wakeup events are enabled/disabled using PM_WKEN1_CORE/PM_WKEN_PER regs. Add api to control the module level wakeup mechanism from info provided from hwmod data. omap_hwmod_enable/disable_wakeup is used from serial.c which should configure PM_WKEN register to enable or disable the module level wakeup. Cc: Tero Kristo <t-kristo@ti.com> Cc: Tony Lindgren <tony@atomide.com> Cc: Paul Walmsley <paul@pwsan.com> Cc: Kevin Hilman <khilman@ti.com> Cc: Benoit Cousson <b-cousson@ti.com> Cc: Rajendra Nayak <rnayak@ti.com> Cc: Santosh Shilimkar <santosh.shilimkar@ti.com> Signed-off-by: Govindraj.R <govindraj.raja@ti.com>
2012-07-10HWMOD: Fix to disable dma to allow system to go to OFFKishon Vijay Abraham I
During _reset of the (hwmod)device, the dmadisable is set so that it does not prevent idling of the system. (NOTE: having dmadisable to 0, prevents the system to idle) Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com> Signed-off-by: Huzefa Kankroliwala <huzefank@ti.com> Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2012-07-10ARM: omap: hwmod: warn only when clkdm is missing from both clk and hwmodRajendra Nayak
On OMAP4+, the clkdm association is moved to hwmod while on older OMAPs' its associated with a clk. Hence look for a clkdm in both clk and hwmod and warn only when its missing in both. Also fix the pr_warning() to print the correct hwmod name. Signed-off-by: Rajendra Nayak <rnayak@ti.com>
2012-07-10ARM: OMAP2+: hwmod: add omap_hwmod_get_main_clk() APITarun Kanti DebBarma
Add an API to get main clock name associated with a given @oh. This will avoid the need to construct fclk names during early initialization in order to get fclk handle using clk_get(). Cc: Cousson, Benoit <b-cousson@ti.com> Cc: Paul Walmsley <paul@pwsan.com> Cc: Tony Lindgren <tony@atomide.com> Cc: Kevin Hilman <khilman@ti.com> Cc: Rajendra Nayak <rnayak@ti.com> Cc: Santosh Shilimkar <santosh.shilimkar@ti.com> Signed-off-by: Tarun Kanti DebBarma <tarun.kanti@ti.com>
2012-07-10ARM: OMAP: hwmod: Fix error handling in functions used OMAP4 onwardsRajendra Nayak
Some functions like _omap4_disable_module() and _omap4_wait_target_disable() are (will be) used on all OMAPs OMAP4 and beyond which support module level control. Fix the error checks in these functions to return if called on any platform pre OMAP4 (i.e OMAP2 and OMAP3) instead of checking for !cpu_is_omap44xx(). This avoids having to update the error check with a '&& !cpu_is_omap54xx()' when OMAP5 is introduced and possibly similar updates when further OMAP generations are added. Signed-off-by: Rajendra Nayak <rnayak@ti.com>
2012-07-10arm: omap: devices: add support for registering rprm regulatorsSuman Anna
The regulators are usually defined in the board file, and support has been added to publish the regulator data relevant to the remote processor resource manager. This data would be used by the generic rpmsg resmgr driver layer to request/release and control a regulator on behalf of the remote processor through the rpmsg resmgr framework. Change-Id: I901b6c215d9307ea4a28ff191dcf1dec76233686 Signed-off-by: Suman Anna <s-anna@ti.com> Signed-off-by: Subramaniam Chanderashekarapuram <subramaniam.ca@ti.com> Signed-off-by: Fernando Guzman Lugo <fernando.lugo@ti.com>
2012-07-10ARM: OMAP5: Fix AESS init modpost warningMisael Lopez Cruz
AESS device creation occurs only during initialization, hence fix below modpost check warning by marking omap_init_aess() function as __init. "WARNING: vmlinux.o(.text+0x1f2b0): Section mismatch in reference from the \ function omap_init_aess() to the function .init.text:omap_device_build() The function omap_init_aess() references the function __init omap_device_build(). This is often because omap_init_aess lacks a __init annotation or the annotation of omap_device_build is wrong." Change-Id: I8f21e687c1817de0e945ab716e9401449b4ec05a Signed-off-by: Misael Lopez Cruz <misael.lopez@ti.com>
2012-07-10OMAP: devices: Make sure VXREC device is included as a module.Liam Girdwood
Change-Id: I4db4159c0ca217268b7cce8ffdc5c3bbb82a85a8 Signed-off-by: Liam Girdwood <lrg@ti.com>
2012-07-10arm: omap: device: create a device for system control moduleKishon Vijay Abraham I
Extracts the device data from hwmod database and create a platform device using omap device build. The device build is done during postcore_initcall. Change-Id: I153d9dd5f4139d43e408d8ed1b0c641868821623 Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com> Signed-off-by: Eduardo Valentin <eduardo.valentin@ti.com> Signed-off-by: Radhesh Fadnis <radhesh.fadnis@ti.com>
2012-07-10OMAP4: VxREC: register VxREC platform deviceSebastien Guiriec
Signed-off-by: Francois Mazard <f-mazard@ti.com> Signed-off-by: Pierre Moos <p-moos@ti.com> Signed-off-by: Sebastien Guirec <s-guiriec@ti.com>
2012-07-10ARM: OMAP4+: devices: Add McASP.Sebastien Guiriec
Add McASP platform device for OMAP4/5 Signed-off-by: Sebastien Guiriec <s-guiriec@ti.com>
2012-07-10rpmsg: resmgr: omap: request auxclk based on idsFernando Guzman Lugo
The current rpmsg resmgr implementation for auxclks is based on the clock names being supplied from the remote processor. The number of auxclks and the associated clock names can vary from one OMAP version to another and are defined using clock data on the Linux-side. This implemenation is changed to use ids so that the remote processor code can remain agnostic of the clock names. The number and clock names are published in the mach layer, and the generic rpmsg resmgr omap layer queries the names associated with an id by using a auxclk_lookup ops function defined in the MACH layer. Change-Id: Ie7b7d4fa3d143d2d267a447805ba12305f2c8c61 Signed-off-by: Fernando Guzman Lugo <fernando.lugo@ti.com> Signed-off-by: Subramaniam Chanderashekarapuram <subramaniam.ca@ti.com> Signed-off-by: Suman Anna <s-anna@ti.com>
2012-07-10rpmsg: resmgr: omap: request regulator based on idsFernando Guzman Lugo
There can be any number of different regulators that needs to be controlled from the remote processor and these are specific to each board. The corresponding mach layer provides a new op to get the desired regulator data, and this can looked up using a platform agnostic id. The specific rprm regulator data has provision to identify whether a regulator voltage is fixed or variable, and this info is used accordingly in calling the regulator_set_voltage API. Change-Id: I335fdc66eae1c4b2318074ec09d7d3441ad237b3 Signed-off-by: Fernando Guzman Lugo <fernando.lugo@ti.com> Signed-off-by: Subramaniam Chanderashekarapuram <subramaniam.ca@ti.com> Signed-off-by: Suman Anna <s-anna@ti.com>
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-17 21:29:35 +0000