summaryrefslogtreecommitdiff
path: root/3rdparty/chromeec
diff options
context:
space:
mode:
authorDouglas Anderson <dianders@chromium.org>2016-08-04 09:27:40 -0700
committerMartin Roth <martinroth@google.com>2016-08-09 18:01:34 +0200
commit4884c5d52d23ca02be326d41233dc16b829d6535 (patch)
tree97dfb41d7ececb01a466bb604d5e62e190b31efc /3rdparty/chromeec
parent9d130a9e1038e406c4be74a70a99f5530ef5c55d (diff)
google/gru: Fix rk3399-gru write protect
The write protect GPIO is active high, not active low. After fixing I can see this after removing the write-protect screw: $ crossystem | grep wpsw_boot wpsw_boot = 0 Putting the screw in shows: $ crossystem | grep wpsw_boot wpsw_boot = 1 Caution: this CL contains explicit material. It explicitly sets the pullup on the WP GPIO even though that's the boot default. BRANCH=None BUG=chrome-os-partner:55933 TEST=See desc. Change-Id: I23e17e3bbbe7dcd83e81814de46117491e61baaa Signed-off-by: Martin Roth <martinroth@chromium.org> Original-Commit-Id: e6969f4be42c00c6e88bbb14929cf0454462ad21 Original-Change-Id: Ie65db9cf182b0a0a05ae412f86904df6b239e0f4 Original-Signed-off-by: Douglas Anderson <dianders@chromium.org> Original-Reviewed-on: https://chromium-review.googlesource.com/366131 Original-Tested-by: Brian Norris <briannorris@chromium.org> Original-Reviewed-by: Julius Werner <jwerner@chromium.org> Reviewed-on: https://review.coreboot.org/16115 Tested-by: build bot (Jenkins) Reviewed-by: Furquan Shaikh <furquan@google.com>
Diffstat (limited to '3rdparty/chromeec')
0 files changed, 0 insertions, 0 deletions