> > + synchronize_irq(iproc_i2c->irq); > > If one takes a look at the I2C slave ISR routine, there are places where > IRQ can be re-enabled in the ISR itself. What happens after we mask all > slave interrupt and when 'synchronize_irq' is called, which I suppose is > meant to wait for inflight interrupt to finish where there's a chance > the interrupt can be re-enable again? How is one supposed to deal with that? I encountered the same problem with the i2c-rcar driver before I left for my holidays. > > + iproc_i2c->slave = NULL; > > + > > /* Erase the slave address programmed */ > > tmp = iproc_i2c_rd_reg(iproc_i2c, S_CFG_SMBUS_ADDR_OFFSET); > > tmp &= ~BIT(S_CFG_EN_NIC_SMB_ADDR3_SHIFT); > >
Attachment:
signature.asc
Description: PGP signature
