summaryrefslogtreecommitdiff
path: root/driver/tcpm/stub.c
diff options
context:
space:
mode:
authorDenis Brockus <dbrockus@chromium.org>2019-12-10 10:24:12 -0700
committerCommit Bot <commit-bot@chromium.org>2019-12-12 03:53:55 +0000
commit896271dad5edbfaad2b0ff10a6fb1dcfb1143089 (patch)
tree01ae1278294b969fc70d0b6f15f963b2c2bc7e19 /driver/tcpm/stub.c
parent40b6c5de590e6290e6b516c380f6b59efbff4fa3 (diff)
downloadchrome-ec-896271dad5edbfaad2b0ff10a6fb1dcfb1143089.tar.gz
tcpci: change connect to auto discharge disconnect
It was originally thought the connect/disconnect would be a good generic way to set/clear auto_discharge_disconnect but it was not working reliably. Although the points that we are calling to perform this enable/disable are close to the connect/disconnect, there is more fine tuning required to make this work. BUG=b:144126745,chromium:951683 BRANCH=none TEST=attach/disconnect charger with and without AP running TEST=attach/disconnect device with AP running Change-Id: Ib1418771aec6d0a52895972e4db6881b072c0c3d Signed-off-by: Denis Brockus <dbrockus@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/1960514 Reviewed-by: Edward Hill <ecgh@chromium.org>
Diffstat (limited to 'driver/tcpm/stub.c')
-rw-r--r--driver/tcpm/stub.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/driver/tcpm/stub.c b/driver/tcpm/stub.c
index 0ebe8af999..3626f148fc 100644
--- a/driver/tcpm/stub.c
+++ b/driver/tcpm/stub.c
@@ -89,6 +89,10 @@ int tcpm_set_rx_enable(int port, int enable)
return tcpc_set_rx_enable(port, enable);
}
+void tcpm_enable_auto_discharge_disconnect(int port, int enable)
+{
+}
+
int tcpm_has_pending_message(int port)
{
return !rx_buf_is_empty(port);