summaryrefslogtreecommitdiff
path: root/power
diff options
context:
space:
mode:
authorVadim Bendebury <vbendeb@chromium.org>2016-02-12 14:05:14 -0800
committerchrome-bot <chrome-bot@chromium.org>2016-02-13 20:04:48 -0800
commit80d49a433dd95b243e118c8690ad4e6b1db2b71e (patch)
tree712879e899fe1fe73a4e0d03c40302a5e30596cd /power
parent7dd904b8d339ea5fbcedf596ae74cb512c4d1052 (diff)
downloadchrome-ec-80d49a433dd95b243e118c8690ad4e6b1db2b71e.tar.gz
cr50: modify mpsse to work with the new device
The ultra debug board uses a different FTDI chip (vid:did 0403:6010), which has two ports. The SPI interface on this chip is hooked up to the second port, but the code indiscriminately uses the first port when trying to open the SPI channel, on all devices known to it. Adding a new field in the supported_devices table allows to keep default behavior, but use port B (the second port) when required. Also, fix printout formatting problem. BRANCH=none BUG=chrome-os-partner:37754 TEST=tpmtest succeeds with the new board Change-Id: I01f7937444c8df61d7439a66d9da89fb2cac5372 Signed-off-by: Vadim Bendebury <vbendeb@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/327232 Commit-Ready: Marius Schilder <mschilder@chromium.org> Tested-by: Marius Schilder <mschilder@chromium.org> Reviewed-by: Marius Schilder <mschilder@chromium.org>
Diffstat (limited to 'power')
0 files changed, 0 insertions, 0 deletions