Hi Arnd, >Oh, I see you simply do > > ret = i2c_master_send(client, info->buf, len); > usleep_range(1000, 10000); > >and assume that the buffer can always be written within a >milisecond, so you just slow down output enough to never have >to worry about it, right? > >A nicer solution would be to have an interrupt driven output >so you know when the i2c buffers have been flushed. Well, I get the idea of interrupt driven output, but as I have little linux kernel experience I'm not sure how to implement this. Can you extend you thoughts or if you know piont me a driver which uses that concept? I'm not sure who should rise an interrupt when data has been flushed. I2c core or the chip itself? What's more, I guess the i2c_master_send is a synchronous call and when it returnes we know it flushed data. Right? /Waldek -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
