mb/google/poppy/nocturne: Fix touchscreen reset GPIO config
The touchscreen reset GPIO is configured as PAD_CFG_TERM_GPO with an internal pull-down, which puts it in a state of contention when the reset pin is released / set to high. Fix this by changing the reset GPIO to PAD_CFG_GPO like all other poppy variants use for the touchscreen reset. TEST=build/boot nocturne, touchscreen still works. Change-Id: I1ad4bb9d4194485990f54ffa7bae05f5c9a39deb Signed-off-by: Matt DeVillier <matt.devillier@gmail.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/71185 Reviewed-by: Angel Pons <th3fanbus@gmail.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
This commit is contained in:
parent
7f2c0bf838
commit
3d352a7218
|
@ -220,7 +220,7 @@ static const struct pad_config gpio_table[] = {
|
|||
/* E10 : USB2_OC1# ==> USB_C1_OC_ODL */
|
||||
PAD_CFG_NF(GPP_E10, NONE, DEEP, NF1),
|
||||
/* E11 : USB2_OC2# ==> TOUCHSCREEN_RESET_L */
|
||||
PAD_CFG_TERM_GPO(GPP_E11, 0, DN_20K, DEEP),
|
||||
PAD_CFG_GPO(GPP_E11, 0, DEEP),
|
||||
/* E12 : USB2_OC3# ==> NC */
|
||||
PAD_NC(GPP_E12, NONE),
|
||||
/* E13 : DDPB_HPD0 ==> USB_C1_DP_HPD */
|
||||
|
|
Loading…
Reference in New Issue