From c5f77fa31961d39dd7b4bd2902288ead9ad80100 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: I566c4516b34686b744a47a2b0c18c4b801456727 Signed-off-by: Tom Warren Reviewed-on: https://chromium-review.googlesource.com/224032 Reviewed-by: Aaron Durbin --- 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 8b62c144f5..f3d83c6081 100644 --- a/src/soc/nvidia/tegra132/bootblock.c +++ b/src/soc/nvidia/tegra132/bootblock.c @@ -63,9 +63,6 @@ void main(void) { void *entry = NULL; - // enable pinmux clamp inputs - clamp_tristate_inputs(); - // enable JTAG at the earliest stage enable_jtag();