tuna: remove duplicate call to set vram
android-display manages this now
tuna: remove dsp carveouts
Remove duplicated calls
android-display manages those
tuna: adapt to reserve call to dynamic changes
Since system memory size and carveouts are calculated dynamically,
omap_ion_init() calls should be invoked upfront so as the address
and sizes are initialized properly.
All omap4 board files are updated

Change-Id: I67a87e3d7973dc457d48e1df6a2277fdba09e02e
Signed-off-by: Devaraj Rangasamy <dev@ti.com>
Revert "omap4: sdp/panda/tablet: reserve memory for dsp"

This reverts commit e699cc2c4cc3f369108d83370172138294f9840f.

DSP currently requires 4MB of memory to be set-aside to meet its
firmware requirements and can use either a fixed carveout or
a dynamically assigned carveout. The above commit uses static
carveouts for DSP in various board files. DSP does not have a
mandatory requirement to use this fixed carveout, and has been
switched over to use a dynamically allocated carveout address.
The above commit is therefore being reverted to free up unused
carveout memory.

This change simultaneously fixes a build error when the DSP
remoteproc is included in the build configuration. The build
was by the following commit:
	"OMAP4: ion: remove hardcoded carveout sizes"

Conflicts:

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

Change-Id: Iee9be7dbc19dd580fabce6ae966cf86d1f54b5cb
Signed-off-by: Jesse Villarreal <jesse.villarreal@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>

Conflicts:
	arch/arm/mach-omap2/board-4430sdp.c
	arch/arm/mach-omap2/board-44xx-tablet.c
	arch/arm/mach-omap2/board-omap4panda.c
Revert "remoteproc: add mutex protection for traces"

This reverts commit 565e03c393854495e814342eb3138e21a3de2604.

Conflicts:
	drivers/remoteproc/remoteproc.c
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>
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>
drivers: gpu: ion: add ion_phys_frm_buffer
[moto] drivers/gpu/ion: add ion_phys_frm_buffer and ion_phys_frm_dev
Remove duplicate ion_phys_frm_dev definition.

Also fix minor whitespace thing.

Signed-off-by: Kyle Repinski <repinski23@gmail.com>