summaryrefslogtreecommitdiff
path: root/chip/stm32/usb.c
diff options
context:
space:
mode:
authorMary Ruthven <mruthven@chromium.org>2018-01-16 15:26:35 -0800
committerchrome-bot <chrome-bot@chromium.org>2018-01-17 06:20:39 -0800
commit7b5b83055cbf8b4e67e6e63e72dd8f8038f80635 (patch)
tree846e4b77e52c0eecdd8d63a847face0dd5739821 /chip/stm32/usb.c
parente71899a5734b151b79db896b88f00cac14b8e50a (diff)
downloadchrome-ec-7b5b83055cbf8b4e67e6e63e72dd8f8038f80635.tar.gz
cr50:ap_state: reenable detect ap on interrupt
ap_state doesn't disable/enable the detect ap interrupt correctly. This means cr50 is mostly just polling the AP state. Cr50 may not realize the AP is up until almost a second after it first turned on. This change reenables the detect ap on interrupt while debouncing the AP state or if Cr50 thinks the AP is off, so cr50 can more quickly detect the transition from off to on. This issue doesn't affect devices that detect the AP with TPM_RST_L, because we never disable the TPM_RST_L interrupt and that handler calls ap_on_deferred directly. BUG=b:71866206 BRANCH=cr50 TEST=run power_state:rec on Dru and make sure there are no tpm irq timeouts. Change-Id: I67388f9dce94fb22efe5755a0de563e5af42f8f5 Signed-off-by: Mary Ruthven <mruthven@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/869410 Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'chip/stm32/usb.c')
0 files changed, 0 insertions, 0 deletions