From fe9e3bf56532b33a9d99b9372b53905dece5907b Mon Sep 17 00:00:00 2001 From: Randall Spangler Date: Tue, 9 Jun 2015 11:15:06 -0700 Subject: Remove obsolete board-specific code Now that we've removed boards from ToT, also delete board-specific code used only by the removed boards. There are still more things to remove (unused charging chips, LED drivers, COMx support). More CLs coming. BUG=chromium:493866 BRANCH=none TEST=make buildall -j Change-Id: Ie6bdeaf96e61cadd77e3f6336c73b9b54ff4eabb Signed-off-by: Randall Spangler Reviewed-on: https://chromium-review.googlesource.com/276524 Reviewed-by: Alec Berg --- util/flash_pd.py | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) (limited to 'util/flash_pd.py') diff --git a/util/flash_pd.py b/util/flash_pd.py index f3e9aaeca9..bc9eab1996 100755 --- a/util/flash_pd.py +++ b/util/flash_pd.py @@ -37,12 +37,11 @@ class FlashPDError(Exception): class FlashPD(client.ServoClient): """class to flash PD MCU. - Note, - Some designs(samus) have multiple embedded MCUs. In that case the convention - is to name the pty associated with usbpd as 'usbpd_uart_pty'. In the case - where there is only one MCU (fruitpie) we prefer 'usbpd_uart_pty' but will - also associate 'ecu_uart_pty' with having capability to flash the UBS-PD - capable PSU(zinger). + Note, Some designs(samus) have multiple embedded MCUs. In that case + the convention is to name the pty associated with usbpd as + 'usbpd_uart_pty'. In the case where there is only one MCU we prefer + 'usbpd_uart_pty' but will also associate 'ecu_uart_pty' with having + capability to flash the USB-PD capable PSU(zinger). Attributes: _options : Values instance from optparse. -- cgit v1.2.1