[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4b939e17-f364-4e63-f254-17bd531f75e6@fb.com>
Date: Fri, 21 Jun 2019 22:21:23 +0000
From: Tao Ren <taoren@...com>
To: Ryan Chen <ryan_chen@...eedtech.com>,
Brendan Higgins <brendanhiggins@...gle.com>
CC: Mark Rutland <mark.rutland@....com>,
devicetree <devicetree@...r.kernel.org>,
"linux-aspeed@...ts.ozlabs.org" <linux-aspeed@...ts.ozlabs.org>,
OpenBMC Maillist <openbmc@...ts.ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [Potential Spoof] Re: [PATCH 1/2] i2c: aspeed: allow to customize
base clock divisor
On 6/20/19 1:13 AM, Tao Ren wrote:
> On 6/20/19 1:01 AM, Ryan Chen wrote:
>> Hello Tao,
>> Let me more clear. When you set (3, 15, 14) the device sometimes response nack.
>> but when you set (4, 7, 7), the device always ack. Am I right?
>> Ryan
>
> Hello Ryan,
>
> It's correct. We have seen the problem on 2 Facebook BMC platforms so far. Given the other ~10 Facebook BMC platforms are still running kernel 4.1 (with (4, 7, 7) settings), I'd assume more platforms will be impacted after upgrading to the latest kernel.
>
> Thank you for spending time on this!
Just heads up Ryan and I are working with ODM vendors to collect scope output; will update back when we have new findings. Thank you all for spending time on this.
Cheers,
Tao
Powered by blists - more mailing lists