summaryrefslogtreecommitdiff
path: root/board/shuboz/board.c
diff options
context:
space:
mode:
authorTing Shen <phoenixshen@google.com>2022-04-29 16:50:23 +0800
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>2022-05-27 07:50:04 +0000
commit5762329719d76c23d395c3816ed503597c4f6cc7 (patch)
tree734132588794da2fcb2dcfb45fe60bdf802ab00f /board/shuboz/board.c
parentc753fad6a886ae257c5b6e415eb146cff45f6d0b (diff)
downloadchrome-ec-5762329719d76c23d395c3816ed503597c4f6cc7.tar.gz
usbc: fix the VID and PID field in Battery_Capabilities
When responding to an invalid Get_Battery_Cap request, Set VID:PID field to FFFF:0000 according to PD 3.1 spec below. Also rearranged the logic to handle invalid battery ref in a single place. -- 6.5.5.1 If the Battery Cap Ref field in the Get_Battery_Cap Message is Invalid, this VID field Shall be 0xFFFF. 6.5.5.2 The following rules apply to the PID field. When the VID: <skipped...> - Is 0xFFFF the PID field Shall be set to 0x0000. BUG=b:229700747 TEST=pass TEST.PD.PROT.PORT3.4 BRANCH=none Signed-off-by: Ting Shen <phoenixshen@google.com> Change-Id: Ie7e9fbfeba8d9e9980c03a5cef0773492e39733a Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3614529 Commit-Queue: Ting Shen <phoenixshen@chromium.org> Reviewed-by: Eric Yilun Lin <yllin@google.com> Tested-by: Ting Shen <phoenixshen@chromium.org>
Diffstat (limited to 'board/shuboz/board.c')
0 files changed, 0 insertions, 0 deletions