summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndrew Jeffery <andrew@aj.id.au>2017-03-24 04:13:22 +0300
committerJoel Stanley <joel@jms.id.au>2017-03-24 05:56:16 +0300
commitf80ce42a332cd296d698fb5996dd18f785f63e79 (patch)
tree7523c37474abb2ffe83e94b98e6914f186b18f24
parentd3634484d104ee5961d81662cacec56fef6fc90f (diff)
downloadlinux-f80ce42a332cd296d698fb5996dd18f785f63e79.tar.xz
ARM: dts: Disable UCD90160 in the Witherspoon dts
This is a work-around for the lack of PGOOD issue: https://github.com/openbmc/openbmc/issues/832 Binding the UCD9000 driver to the device (and possibly the sequence of unbinding, poking the UCD90160 via i2cset, then re-binding the UCD9000 driver) appears to have some negative effects. Instrumenting the transactions with reads of the PMBus status tree lead to the following observations under "normal" operation. Reduce our problems by communicating with the UCD90160 as little as possible. With the associated userspace change, the only communication will be applying the VCS work-around. Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Tested-by: Uma Yadlapati <yadlapat@us.ibm.com> Signed-off-by: Joel Stanley <joel@jms.id.au>
-rw-r--r--arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts2
1 files changed, 2 insertions, 0 deletions
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts b/arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts
index 4d26d4702a34..6e7b5a48f383 100644
--- a/arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts
+++ b/arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts
@@ -253,6 +253,8 @@
};
ucd90160@64 {
+ /* https://github.com/openbmc/openbmc/issues/832 */
+ status = "disabled";
compatible = "ti,ucd90160";
reg = <0x64>;
};