[PATCH] ARM: aspeed: Disable UCD90160 in the Witherspoon devicetree

[Joel Stanley]

On Fri, Mar 24, 2017 at 11:43 AM, Andrew Jeffery <andrew at aj.id.au> wrote:
> This is a work-around for [1]. 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.
>
> [1] https://github.com/openbmc/openbmc/issues/832
>
> 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 at aj.id.au>

Applied to dev-4.7 with the above commit message, and a Tested-by from Uma.

Cheers,

Joel

> ---
>  arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts b/arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts
> index 4d26d4702a34..69d5897dbfde 100644
> --- a/arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts
> +++ b/arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts
> @@ -253,6 +253,7 @@
>         };
>
>         ucd90160 at 64 {
> +               status = "disabled";
>                 compatible = "ti,ucd90160";
>                 reg = <0x64>;
>         };
> --
> 2.9.3
>