i2c almost working for me, was Re: i2c still not working for me

[Daniel Braniss]

> On 11 Apr 2019, at 09:56, Daniel Braniss <danny at cs.huji.ac.il> wrote:
> 
> if no device is connected, I2CRDWR hangs, 
> it also happens with i2c(8) -s, only reboot helps.
> 
> ichb1: twsi_reset: Using IIC_FASTEST/UNKNOWN mode with speed param=2a
> iichb1: TWSI_WRITE: Writing 0 to 18
> iichb1: TWSI_WRITE: Writing 2a to 14
> iichb1: TWSI_WRITE: Writing 40 to c
> iichb1: TWSI_WRITE: Writing c4 to c
> iichb1: twsi_transfer: transmitting 2 messages
> iichb1: TWSI_READ: read f8 from 10
> iichb1: twsi_transfer: status=f8
> iichb1: twsi_transfer: msg[0] flags: 0
> iichb1: twsi_transfer: msg[0] len: 9
> iichb1: TWSI_WRITE: Writing e4 to c
> 
> and now it’s hung
[…]


even with a working device, this happens sometimes:

my app gets ENXIO from the ioctl(fd, I2CRDWR, &data) and on the console:
…
gic0: Spurious interrupt detected: last irq: 38 on CPU2
gic0: Spurious interrupt detected: last irq: 38 on CPU2
gic0: Spurious interrupt detected: last irq: 38 on CPU2
gic0: Spurious interrupt detected: last irq: 29 on CPU2
gic0: Spurious interrupt detected: last irq: 29 on CPU2
gic0: Spurious interrupt detected: last irq: 38 on CPU2
gic0: Spurious interrupt detected: last irq: 29 on CPU2
gic0: Spurious interrupt detected: last irq: 38 on CPU2
gic0: Spurious interrupt detected: last irq: 29 on CPU2
gic0: Spurious interrupt detected: last irq: 38 on CPU2
gic0: Spurious interrupt detected: last irq: 38 on CPU2
gic0: Spurious interrupt detected: last irq: 38 on CPU2
gic0: Spurious interrupt detected: last irq: 38 on CPU2
gic0: Spurious interrupt detected: last irq: 38 on CPU2
gic0: Spurious interrupt detected: last irq: 38 on CPU2
gic0: Spurious interrupt detected: last irq: 38 on CPU2
gic0: Spurious interrupt detected: last irq: 38 on CPU2
gic0: Spurious interrupt detected: last irq: 29 on CPU2
gic0: Spurious interrupt detected: last irq: 29 on CPU2
gic0: Spurious interrupt detected: last irq: 29 on CPU2

the good news: my app is killable :-)