bluetooth: set rfkill state before register it

rfkill_register was turning on bluetooth module by accident because
rfkill state was not set. The default setting was used which happened to
be turning on bluetooth.
Also remove a uncessary poweroff call.

Change-Id: I54255bdd7b48d31ef74eb385cdc2327ea07c7f03
bluetooth: cleanup BT_HOST_WAKE_INT_ENABLED handling

Change-Id: Ic95be267636920be8c515151585123295e47bcf5
bluetooth: remove BT_RESET_GPIO calls via CONFIG_BLUETOOTH_USES_COMBINED_GPIO define

Change-Id: I16849f33c58f9e4645c18611f23fa05555a9cda3
Revert "Revert "OMAP4: HWMOD: UART2: disable smart-idle.""

This reverts commit a472483e295e788ef0e7ad58bc4e6c00db66b938.
ARM: omap4: tuna: bluetooth: set autosuspend delay to 0

The uart state is controlled by the BT_WAKE and BT_WAKE_HOST
gpios, disable autosuspend.  This prevents UART2 being stuck
on in suspend sometimes.

Change-Id: I77a83e42134f6a63020583b46b01ff7289de5bb3
bluetooth: remove insane debugging and make sure errors are logged

Change-Id: I4e34c9858755c5e93af72259bd9fc8c8e51bb846
Merge remote-tracking branch 'kfire/cm-10.1' into cm-10.1-exp