RE: [PATCH 1/2] i2c: aspeed: allow to customize base clock divisor
From: Ryan Chen
Date: Thu Jun 20 2019 - 04:07:22 EST
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?
From: Tao Ren [mailto:taoren@xxxxxx]
Sent: Thursday, June 20, 2019 3:57 PM
To: Ryan Chen <ryan_chen@xxxxxxxxxxxxxx>; Brendan Higgins <brendanhiggins@xxxxxxxxxx>
Cc: Mark Rutland <mark.rutland@xxxxxxx>; devicetree <devicetree@xxxxxxxxxxxxxxx>; linux-aspeed@xxxxxxxxxxxxxxxx; OpenBMC Maillist <openbmc@xxxxxxxxxxxxxxxx>; Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>; Rob Herring <robh+dt@xxxxxxxxxx>; Linux ARM <linux-arm-kernel@xxxxxxxxxxxxxxxxxxx>; linux-i2c@xxxxxxxxxxxxxxx
Subject: Re: [PATCH 1/2] i2c: aspeed: allow to customize base clock divisor
On 6/20/19 12:29 AM, Ryan Chen wrote:
> Hello Tao,
> Our recommend about clk divider setting is follow the datasheet clock setting table for clock divisor.
Thanks Ryan for the response. Could you also share some recommendations/hints on how to solve the intermittent i2c transaction failures on Facebook AST2500 BMC platforms?
BTW, the patch is not aimed at modifying the existing formula of calculating clock settings in i2c-aspeed driver: people still get the recommended settings by default. The goal of the patch is to allow people to customize clock settings in case the default/recommended one doesn't work.