EHCI: HSIC: Fix a race between root hub resume and controller removal

The pm_qos request is removed before unregistering the HCD in remove
function. If root hub resume runs in parallel, there is a possibility
of adding the pm_qos request back to the active list. The pm_qos request
memory is freed after unregistering the HCD and this would lead to
pm_qos list corruption. A crash is observed when another driver is
submitting a pm_qos request after HSIC controller is removed during
shutdown.  Remove HCD prior to releasing controller resources.

CRs-Fixed: 444928
Change-Id: Iaed6964e7d4245b8ae6c295ed6c76f5a9d32e20f
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
USB: ehci_hcd: Don't panic on receiving FATAL ERROR

"commit 105d07f EHCI: HSIC: Add debug support for HSIC system error"
 has introduced panic() on receiving FATAL STATUS interrupt. For OTG
and 2nd/3rd HSUSB instance this panic() is not required as the system
can be functional with USB system error, hence avoiding this panic()
for OTG and 2nd/3rd HSUSB instances.

CRs-Fixed: 447040
Change-Id: I94dc63c5e8ac612ce9bbe42d2ef8266816be2693
Signed-off-by: Chiranjeevi Velempati <cvelempa@codeaurora.org>
EHCI: HSIC: disable pm runtime device before remove hcd

Merge order of commits 21a480e and e50d914 introduced runtime pm
disable depth counter imbalance fixed by e50d914 again. Fix the
bug by disabling runtime pm before removing HCD.

Change-Id: I249a4f63db3a975652e6ce15545584e41bae284b
Signed-off-by: Ido Shayevitz <idos@codeaurora.org>