• David S. Miller's avatar
    niu: Fix readq implementation when architecture does not provide one. · e23a59e1
    David S. Miller authored
    This fixes a TX hang reported by Jesper Dangaard Brouer.
    
    When an architecutre cannot provide a fully functional
    64-bit atomic readq/writeq, the driver must implement
    it's own.  This is because only the driver can say whether
    doing something like using two 32-bit reads to implement
    the full 64-bit read will actually work properly.
    
    In particular one of the issues is whether the top 32-bits
    or the bottom 32-bits of the 64-bit register should be read
    first.  There could be side effects, and in fact that is
    exactly the problem here.
    
    The TX_CS register has counters in the upper 32-bits and
    state bits in the lower 32-bits.  A read clears the state
    bits.
    
    We would read the counter half before the state bit half.
    That first read would clear the state bits, and then the
    driver thinks that no interrupts are pending because the
    interrupt indication state bits are seen clear every time.
    
    Fix this by reading the bottom half before the upper half.
    Tested-by: default avatarJesper Dangaard Brouer <jdb@comx.dk>
    Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    e23a59e1
niu.c 203 KB