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/omap_hsi.c
	arch/arm/mach-omap2/pm44xx.c
	drivers/omap_hsi/hsi_driver.c
OMAP4+: HSI: Aligned HSR FSM control onto CAWAKE detection

HSR FSM enables the ACREADY to go to 1 and allows reception.
With previous code, HSR FSM is enabled/disabled when clocks are enabled/disabled.
But HSR FSM control shall be separated from HST state, and depend only on CAWAKE.

Now HSR FSM is disabled/enabled when CAWAKE is low/high.

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

Conflicts:
	drivers/omap_hsi/hsi_driver.c
Fix some HSI merge conflict