i2c error for ME port

[Vijay Khemka]

On 11/25/19, 12:21 PM, "Jae Hyun Yoo" <jae.hyun.yoo at linux.intel.com> wrote:

    Hi Vijay,
    
    On 11/25/2019 11:41 AM, James Feist wrote:
    > On 11/25/19 11:39 AM, Vijay Khemka wrote:
    >> Hi James/Jason,
    > 
    > + Jae, any ideas?
    > 
    > 
    >>
    >> I am seeing following i2c error on i2c bus connected to ME. It is one 
    >> time output whenever server is powered on or reboot. Please suggest 
    >> you can think of anything here.
    >>
    >> Regards
    >>
    >> -Vijay
    >>
    >> [ 7358.450768] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after 
    >> processed read.
    >>
    >> [ 7358.465565] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after 
    >> processed read.
    >>
    >> [ 7358.480358] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after 
    >> processed read.
    >>
    >> [ 7358.499663] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after 
    >> processed read.
    >>
    >> [ 7358.514873] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after 
    >> processed read.
    >>
    >> [ 7358.591790] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. 
    >> expected 0x80000084, but was 0x00000084
    
    Looks like you set the second slave address for i2c4 bus. It indicates
    'address 2' match event but current driver doesn't handle this event.
    
    Can you share your i2c4 bus node setting in device tree?

&i2c4 {
  status = "okay";
  // BMC Debug Header
  ipmb0 at 10 {
    compatible = "ipmb-dev";
    reg = <0x10>;
    i2c-protocol;
  };
};
    
    Cheers,
    
    Jae