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