diff options
| author | Brian Norris <briannorris@chromium.org> | 2022-08-23 02:45:04 +0300 |
|---|---|---|
| committer | Heiko Stuebner <heiko@sntech.de> | 2022-08-23 15:34:05 +0300 |
| commit | e5467359a725de90b6b8d0dd865500f6373828ca (patch) | |
| tree | 6ef6f86aa26ad8598d4063137382891c22bcd04f /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | 1ea90b2d293fd8b1f3377c9ed08364ff6f2a8562 (diff) | |
| download | linux-e5467359a725de90b6b8d0dd865500f6373828ca.tar.xz | |
arm64: dts: rockchip: Pull up wlan wake# on Gru-Bob
The Gru-Bob board does not have a pull-up resistor on its
WLAN_HOST_WAKE# pin, but Kevin does. The production/vendor kernel
specified the pin configuration correctly as a pull-up, but this didn't
get ported correctly to upstream.
This means Bob's WLAN_HOST_WAKE# pin is floating, causing inconsistent
wakeup behavior.
Note that bt_host_wake_l has a similar dynamic, but apparently the
upstream choice was to redundantly configure both internal and external
pull-up on Kevin (see the "Kevin has an external pull up" comment in
rk3399-gru.dtsi). This doesn't cause any functional problem, although
it's perhaps wasteful.
Fixes: 8559bbeeb849 ("arm64: dts: rockchip: add Google Bob")
Signed-off-by: Brian Norris <briannorris@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Link: https://lore.kernel.org/r/20220822164453.1.I75c57b48b0873766ec993bdfb7bc1e63da5a1637@changeid
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions