tree 55ae4afefb69cb7aafab8d606350d578046d19cf
parent 02d6decf568e0703c75a29fd191ed94e89a6dcaa
author Julius Werner <jwerner@chromium.org> 1506555361 -0700
committer ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> 1508402459 +0000

UPSTREAM: google/gru: Fix pmu1833_volsel handling

RK3399 has a pin that can decide whether GPIO port 1 is driven with 1.8V
or 3.0V. We thought this mechanism was disabled by default, but it turns
out it wasn't. We want to use that pin as an output GPIO on Scarlet so
we need to reconfigure the respective SoC controls before we do that. It
seems that we also need to explicitly pinmux the pin away from that
special function (to normal GPIO) or weird things happen on some boards.

BUG=b:66534913
TEST=Sprinkled several long udelays, poked test points with a
multi-meter on Scarlet.

Change-Id: Ifdda7d55c2156d1d889675afce9df2afc1e1fd83
Signed-off-by: Martin Roth <martinroth@google.com>
Original-Commit-Id: e0459c78e461f2fa3ce9fc7924ccc47a5c2c66be
Original-Change-Id: Ia02cbb4f3b2f14b0d958b84adcddb0c5f4259efa
Original-Signed-off-by: Julius Werner <jwerner@chromium.org>
Original-Reviewed-on: https://review.coreboot.org/21727
Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-on: https://chromium-review.googlesource.com/699382
Commit-Ready: Patrick Georgi <pgeorgi@chromium.org>
Tested-by: Martin Roth <martinroth@chromium.org>
Reviewed-by: Martin Roth <martinroth@chromium.org>
(cherry picked from commit 7d9354f976a51a4a03decc3d5e5a4ced2a491c85)
Reviewed-on: https://chromium-review.googlesource.com/728039
Reviewed-by: Philip Chen <philipchen@chromium.org>
Commit-Queue: Philip Chen <philipchen@chromium.org>
Tested-by: Philip Chen <philipchen@chromium.org>