From 6f9feb4ffb2ca58478265a3f111066cd53cf73ed Mon Sep 17 00:00:00 2001 From: Tom Warren Date: Fri, 17 Oct 2014 10:27:09 -0700 Subject: [PATCH] tegra132: Remove clamp_tristate_inputs() call As per NV SysEng, setting PINMUX_CLAMP_INPUTS=1 is now considered a bad thing. It clamps _all_ tristated inputs to zero, and isn't really the panacea for duplicated pinmux mappings as was stated previously. BUG=None BRANCH=None TEST=Built both Rush and Ryu OK. Tested on Rush, booted kernel OK. Change-Id: I7d6982a18a772efda7f1d3bf0dcb0d4d0a5bed8f Signed-off-by: Patrick Georgi Original-Commit-Id: c5f77fa31961d39dd7b4bd2902288ead9ad80100 Original-Change-Id: I566c4516b34686b744a47a2b0c18c4b801456727 Original-Signed-off-by: Tom Warren Original-Reviewed-on: https://chromium-review.googlesource.com/224032 Original-Reviewed-by: Aaron Durbin Reviewed-on: http://review.coreboot.org/9346 Tested-by: build bot (Jenkins) Reviewed-by: Stefan Reinauer --- src/soc/nvidia/tegra132/bootblock.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/src/soc/nvidia/tegra132/bootblock.c b/src/soc/nvidia/tegra132/bootblock.c index fe7d6f04fa..1c910ad041 100644 --- a/src/soc/nvidia/tegra132/bootblock.c +++ b/src/soc/nvidia/tegra132/bootblock.c @@ -58,9 +58,6 @@ void __attribute__((weak)) bootblock_mainboard_early_init(void) void main(void) { - // enable pinmux clamp inputs - clamp_tristate_inputs(); - // enable JTAG at the earliest stage enable_jtag();