OMAP4: ion: remove hardcoded carveout sizes

These are no longer used as android-display is calculating the
carveout sizes.

Change-Id: I3dcaec56158da1a573cb8de9ec3761db94d1a698
Signed-off-by: Lajos Molnar <lajos@ti.com>
Singed-off-by: Dima Svetlov <svetlov@ti.com>

Conflicts:
	arch/arm/mach-omap2/include/mach/omap4_ion.h

Conflicts:
	arch/arm/mach-omap2/include/mach/omap4_ion.h
omap: ion: define carveouts as per system memory configuration

Carveout address and sizes are hardcoded as per 1GB configuration.
512MB configuration will have reduced carveouts and needs
redifinition of carveouts. Static carveout parameters are made
dynamic and calclulated runtime as per system configuration.

Carveout address,size parameters,calculation are made more
easily readable and perceivable.
All carveout parameter initialization needs to happen at
the earliest possible, which is triggerd by board file.

Change-Id: I32bb9e04ef40f5d7d6f7548bba9ab5878bfcb56d
Signed-off-by: Devaraj Rangasamy <dev@ti.com>
OMAPDSS: DSSCOMP: move device to omap plat to configure tiler1d slot

Different devices will have varying requirements on tiler resources. This
change moves the platform device registration for dsscomp to the omap
platform level so at device initialization time we can set the appropriate
Tiler1D slot size.

Change-Id: I5edf5b7cfb056a45ab038b244d2efc758a840b00
Signed-off-by: Tony Lofthouse <a0741364@ti.com>
Signed-off-by: Lajos Molnar <lajos@ti.com>

Conflicts:
	arch/arm/plat-omap/Makefile
	drivers/video/omap2/dsscomp/gralloc.c
sgx_omaplfb: Create omaplfb platform device file to permit device configuration

Change-Id: Ic790a0440d19d862d981a230470523409b25b9a3
Signed-off-by: Tony Lofthouse <a0741364@ti.com>
Signed-off-by: Gustavo Diaz Prado <a0273371@ti.com>

Conflicts:
	arch/arm/plat-omap/Makefile
board-tuna: add android-display dependencies
tuna: Update defconfig.

Conflicts:
	arch/arm/configs/nuked_defconfig
tuna: remove duplicate call to set vram
android-display manages this now
rpmsg-omx: Use ion abstraction to get handle from PVR fd

PVRExportFDToIONHandles was being called directly by rpmsg-omx.
This is now abstracted by ion and drivers should use
omap_ion_fd_to_handles instead.

Change-Id: I2f750887a048eb3d9cd28cdc9c4b08eb3e83e31b
Signed-off-by: Hemant Hariyani <hemanthariyani@ti.com>

Conflicts:
	drivers/rpmsg/rpmsg_omx.c
rpmsg: omx: implement separate register ioctl for sgx buffers

This implements a new register ioctl specifically meant for sgx
buffers. rpmsg_omx clients are expected to call register ioctl
for the specific buffer type (ion or sgx) before sending a buffer
to .write for mapping. The registration allows the rpmsg_omx
driver to hold a reference to the ion buffers making up the sgx
buffer, thereby preventing the buffer(s) to be freed up from
under the remote processor.

The individual imported ion handles are expected to be passed
into the .write call.

When a client no longer expects remote processor to use the buffer,
client should call unregister ioctl. A separate unregister ioctl
for pvr buffers is not created, and the same ion unregister ioctl
is expected to be used for all the ion handles a sgx buffer is
comprised of.

Change-Id: Ib36aab90136627899e98717aeb29bfa637ec09fd
Signed-off-by: Tyler Luu <tluu@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>
rpmsg: omx: add ion system heap to omx ion client

Allow the rpmsg omx ion client to access buffers from
the ion system heap.

Change-Id: Ic2d6922cb5cb05ec96f807a36b77c124769f4ef2
Signed-off-by: Tyler Luu <tluu@ti.com>
Signed-off-by: David Schleef <ds@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>
rpmsg: omx: add handling of ion system heap buffers

Conflicts:
	drivers/rpmsg/rpmsg_omx.c
rpmsg: omx: return correct handle count in 'OMX_IOCPVRREGISTER'

omap_ion_share_fd_to_buffers is always returning 2 in num_handles
even for fd's pointing to 1D memory. In order to return the correct
number of handles to rpmsg client in this ioctl call, 'break' out
of for loop instead of continuing.

Change-Id: Ic7fecc682895a63ad7b7f74b8824f0dc0eb57481
Signed-off-by: Emilian Peev <epeev@mm-sol.com>
Signed-off-by: Tyler Luu <tluu@ti.com>
omap: ion: defining a new Ion 1D heap for WFD HDCP

Conflicts:
	arch/arm/mach-omap2/board-bowser.c
	arch/arm/mach-omap2/board-omap4panda.c
	arch/arm/mach-omap2/omap4_ion.c

Conflicts:
	include/linux/omap_ion.h
tuna: update to latest kernel changes.

Conflicts:
	arch/arm/mach-omap2/board-tuna.c
tuna: Add identifiers for toro HW revs 0x0a and 0x0e.
regulator undervolt

Conflicts:
	arch/arm/mach-omap2/board-tuna.c
regulator work from ch33kybutt
 OMAP4: Enable wake-up feature for sys_nirq2

sys_nirq2 pin is used for twl6040 interrupt line which handles
events (like headset plug detection) that may need to wake-up the
device.

Change-Id: I5480a533116096be7678f516e31952a887b22e38
Signed-off-by: Krishnan Vaidyanathan <krishnanvv@ti.com>
Signed-off-by: Misael Lopez Cruz <misael.lopez@ti.com>

    icepeda-panda-4aj22

Conflicts:
	arch/arm/boot/zImage

Conflicts:
	arch/arm/mach-omap2/board-omap4panda.c
build fix
misc build fix ups