diff options
author | Ye Li <ye.li@nxp.com> | 2016-11-17 16:54:56 +0800 |
---|---|---|
committer | Ye Li <ye.li@nxp.com> | 2016-11-22 17:49:33 +0800 |
commit | 8dfdf83abaff44efb487f801cd1757a729d427c5 (patch) | |
tree | e8634626a97b3afd352fded4f099e92568292a8b /board/astro | |
parent | 1ac22cabb96a14ac4ca58df60ae2025fb5e94db6 (diff) | |
download | u-boot-imx-8dfdf83abaff44efb487f801cd1757a729d427c5.zip u-boot-imx-8dfdf83abaff44efb487f801cd1757a729d427c5.tar.gz u-boot-imx-8dfdf83abaff44efb487f801cd1757a729d427c5.tar.bz2 |
MLK-13450-15 ehci-mx6: Add powerup_fixup implementation
When doing port reset, the PR bit of PORTSC1 will be automatically
cleared by our IP, but standard EHCI needs explicit clear by software. The
EHCI-HCD driver follow the EHCI specification, so after 50ms wait, it
clear the PR bit by writting to the PORTSC1 register with value loaded before
setting PR.
This sequence is ok for our IP when the delay time is exact. But when the timer
is slower, some bits like PE, PSPD have been set by controller automatically
after the PR is automatically cleared. So the writing to the PORTSC1 will overwrite
these bits set by controller. And eventually the driver gets wrong status.
We implement the powerup_fixup operation which delays 50ms and will check
the PR until it is cleared by controller. And will update the reg value which is written
to PORTSC register by EHCI-HCD driver. This is much safer than depending on the delay
time to be accurate and aligining with controller's behaiver.
Signed-off-by: Ye Li <ye.li@nxp.com>
Diffstat (limited to 'board/astro')
0 files changed, 0 insertions, 0 deletions