lkml.org 
[lkml]   [2023]   [Oct]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 6/6] i3c: master: svc: fix random hot join failure since timeout error
    Hi Frank,

    Frank.li@nxp.com wrote on Tue, 17 Oct 2023 10:45:14 -0400:

    > On Tue, Oct 17, 2023 at 04:33:35PM +0200, Miquel Raynal wrote:
    > > Hi Frank,
    > >
    > > Frank.Li@nxp.com wrote on Mon, 16 Oct 2023 11:32:32 -0400:
    > >
    > > > master side report:
    > > > silvaco-i3c-master 44330000.i3c-master: Error condition: MSTATUS 0x020090c7, MERRWARN 0x00100000
    > > >
    > > > BIT 20: TIMEOUT error
    > > > The module has stalled too long in a frame. This happens when:
    > > > - The TX FIFO or RX FIFO is not handled and the bus is stuck in the
    > > > middle of a message,
    > > > - No STOP was issued and between messages,
    > > > - IBI manual is used and no decision was made.
    > > > The maximum stall period is 10 KHz or 100 μs.
    > > >
    > > > This is a just warning. System irq thread schedule latency is possible
    > >
    > > can be bigger
    > > > bigger than 100us. Just omit this waring.
    > >
    > > I'm not sure this is the correct approach. It's a real issue but there
    > > is not much we can do about it. Perhaps dev_err is too high, but I
    > > would not entirely drop this message. Maybe a comment and turning the
    > > message into a dbg printk would be more appropriate?
    >
    > The key is not message. It return true, means IBI/HJ thread will not run.

    But why should the workers run if it's too late?

    Thanks,
    Miquèl

    \
     
     \ /
      Last update: 2023-10-17 17:08    [W:2.629 / U:0.236 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site