New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 614384 link

Starred by 1 user
Status: WontFix
Owner:
█ sha...@chromium.org
Last visit > 30 days ago
Closed: Sep 2017
Cc:
█ vpalatin@chromium.org
adurbin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

ec: pd: consider removing board_reset_pd_mcu() for boards without PD MCU

Project Member Reported by sha...@chromium.org, May 24 2016 
The call to board_reset_pd_mcu() in common/system.c should probably be behind CONFIG_HOSTCMD_PD (not HAS_TASK_PDCMD) so that we're only doing a reset if we have an actual PD MCU. AFAIK, the only reason we need to reset here at all is to put the PD MCU back into RO.

Comment 1 by gkihumba@google.com, Mar 31 2017

Status: Assigned (was: Untriaged)

Comment 2 by sha...@chromium.org, Sep 1 2017

Status: WontFix (was: Assigned)
We're actually using board_reset_pd_mcu() on new boards to HW reset TCPCs now (important for parts that support FW update), so the function can stay.
►

Sign in to add a comment