OMAP4: HSI: mux: use hwmod muxing framework

Use HWMOD dynamic muxing framework.
Only Port 1 is supported for now.

Note: In order to have omap_hsi device registration done after muxing
framework, delayed it to arch_initcall instead of postcore_initcall.

Change-Id: I6b9f9c6041f13ea35ccec41e7f82397eab7ce48e
Signed-off-by: Djamil Elaidi <d-elaidi@ti.com>

Conflicts:
	arch/arm/mach-omap2/omap_hsi.c
OMAP4: HSI: mux: remove unused mux platform data

Since we now use HWMOD muxing feature, many platform data and functions
are no more needed :

* Switching from HSI wakeup to/from IO daisy chain wakeup and handling of wakeup
  enable bit is now handled directly by HWMOD, so wakeup_enable/disable function
  are removed
* Removed board dependend_suspend callback since all shall be done by
  runtime_pm callbacks. But board_suspend and board_resume specific callback are
  kept to handle board dependend specific actions.
* Also aligned to same parameters for board_resume and board_suspend.
* Removed some mux hack functions
* Removed mux reference in platform data

Change-Id: I89a1b545d6e722c0ab19612f9b1f6a0892a0b455
Signed-off-by: Djamil Elaidi <d-elaidi@ti.com>

Conflicts:
	arch/arm/mach-omap2/pm44xx.c
OMAP4: hwmod: change hsi interrupts name

prefixed HSI interrupts with hsi_xxx

Change-Id: I6f45de539e4d2c05924d279b2ce4c2213d89c60b
Signed-off-by: Djamil Elaidi <d-elaidi@ti.com>
OMAP4: ion: Calculate carveout addresses based on sizes

Calculate carveout addresses somewhat dynamically.

- calculate the carveout addresses based on starting or ending
address and size.

- get the tiler2D and nonsecure tiler2D sizes from a separate
platform config variable

- lay out nonsecure tiler2D carveout before tiler2D carvout.
This allows only aligning the sum of these two carveout to
2MB, instead of the size of each.

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

Conflicts:
	arch/arm/mach-omap2/omap4_ion.c
Merge branch 'exp' into stable
OMAPDSS: OMAPFB : Add support for default display scaling.

Currently it is assumed that frame buffer size
is same as default panel size. With this assumption
GFX pipeline is always presented to default display FBDev.
GFX pipeline cannot scale so we cannot have a frame
buffer which is not equal to panel size (LCD | HDMI).
Updated the current logic of omapfb to pick video pipelines
in case scaling is required for FB to be presented to default
panel.

To provide FB size option is provided via command line.
e.g
omapfb.fb_opt=0,720,1280,1,640,480
each element is [fb_ix,width,height]

Change-Id: I9e2d40bed34c5fbf2bac31668d210e0bc586bb40
Signed-off-by: Dandawate Saket <dsaket@ti.com>
Signed-off-by: Muralidhar Dixit <murali.dixit@ti.com>
OMAPFB: Select correct VSYNC IRQ based on DSS channel

Select correct VSYNC IRQ for asynchronous vsync notification
based on the DSS channel.
Current VSYNC notification supports only primary LCD panel.
To support VSYNC notification for default HDMI display this
patch adds the VSYNC IRQ selection based on the DSS channel
for default display.

Change-Id: I0594e80d4b4850c278e6bdd3b07c0cb63488be39
Signed-off-by: Muralidhar Dixit <murali.dixit@ti.com>
OMAP4: OMAPFB: Always set a x_decim and y_decim in overlays

When using the framebuffer API to setup overlay, there's
currently no way to pass a x_decim and y_decim value in
so set some safe non-zero defaults.  Otherwise, when
the overlay is enabled, zero values will cause divide
by zero error in dispc.

Change-Id: Id2cb4bc4cb6be7b57e3ab5fc28fffc57163faecb
Signed-off-by: Mike J. Chen <mjchen@google.com>
Signed-off-by: Ruslan Bilovol <ruslan.bilovol@ti.com>
OMAP4: OMAPFB: Set overlay zorder to 0 if omapfb API used

Since there's no ioctl to set zorder when modifying overlays
using SETUP_PLANE, it's more useful to userland code if
overlay is 0, so they don't have to use sysfs and first
figure out which overlay is being used by omapfb.

Change-Id: I1c2eeecb0b950439e40eec895d6b89c73df2fd7e
Signed-off-by: Mike J. Chen <mjchen@google.com>
Signed-off-by: Ruslan Bilovol <ruslan.bilovol@ti.com>
OMAP4: USB: remove unused function twl6030_set_phy_clk

This function is redundant and not used anywhere.
Remove it and change associated code accordingly

Change-Id: I06ba222429cfe89a401b426a211d1752e646450a
Signed-off-by: Ruslan Bilovol <ruslan.bilovol@ti.com>

Conflicts:
	arch/arm/mach-omap2/board-44xx-power.c
	arch/arm/mach-omap2/board-omap4panda.c
Merge branch 'exp' into stable