Only disable the high-speed device disconnection detction for
level-1 device, or the connection detecting would fail.

Signed-off-by: Jingchang Lu <b35083@freescale.com>

Signed-off-by: Jingchang Lu <b35083@freescale.com>

Detection of high-speed USB device disconnection should be enable
on connection and disable on disconnection.

Signed-off-by: Jingchang Lu <b35083@freescale.com>

- Do not call hcd core adjust wakeup flag code. It may change
wakeup flag, and cause port change detect(PCD) enable setting change.
- For ID wakeup, it should not call host's fsl_usb_recover_hcd at ID interrupt.
The coming ID switch event will resume host.
- Do not need enable wakeup interrupt for host at platform driver resume
routine, it may introduce unnessary wakeup interrupt during bus resume.
The wakeup will be enabled again when usb host goes to controller again
due to autosuspend.
- When there is no gadget enabled, the otg port is still at host mode with
interrupt enabled, so when male Micro-B to female A-type cable with
usb device plugs in, there will be PCD interrupt before hcd core leaves
suspend mode.

Signed-off-by: Peter Chen <peter.chen@freescale.com>

It may be useless at most of platforms, the user can enable discharge
vbus if he/she wants speed up vbus lower speed during OTG switch.

Besides, disable vbus interrupt during vbus change due
to device <--> host mode switch.

Signed-off-by: Peter Chen <peter.chen@freescale.com>

At i.mx6x, the data line (dp and dm) are floating at device mode,
that is to say data line will be any values (0-3.6v).
So if the usb wakeup is enabled, there will be a wakeup interrupt
that causes usb to active mode.

In order to fix this problem well, we need to do below things:
- Need to discharge both dp and dm
- It needs to discharge data line when we switch to device mode and
usb cable is disconnected from the host, but not to disable discharge
after line state is SE0, the reason is that if we do not pulldown
the data line, the line state will be floating again, and possible cause
the wakeup interrupt.
- It needs to disable discharge data line when the usb cable connects at
device mode and usb device is connected at host mode, otherwise it will
affect signal quality.

Signed-off-by: Peter Chen <peter.chen@freescale.com>

The discharge dp function needs to be added at below situation:
- USB cable is disconnected from the PC
- When the usb mode switchs to device mode

Signed-off-by: Peter Chen <peter.chen@freescale.com>

As dp/dm is floating with no usb cable and switch host mode to
device mode situation, it do needs this discharge dp patch
But, discharge vbus doesn't be needed at suspend_irq, so
keep it removing.

This reverts commit 0924b71278650fa3891a8f6ea70f91242ca6e5fd.

Signed-off-by: Peter Chen <peter.chen@freescale.com>

This patch creates two bugs at current i.mx usb framework.
- The high speed device can't be recognized at the first time.
- The usb device can't be recognized after system resume with
usb vbus.

The reason why it creates bugs that it changes (auto)suspend/resume
process for usb core.

This reverts commit e5c4318450e1fe7c61950214e779658c6cea0da7.

Signed-off-by: Peter Chen <peter.chen@freescale.com>

device part

- implement reset_device interface for HSIC host

Signed-off-by: Tony LIU <junjie.liu@freescale.com>