On Thu, Jan 27, 2011 at 01:33:21PM +0100, Jean Delvare wrote: > On Thu, 27 Jan 2011 11:01:06 +0000, Dimitris Papastamos wrote: > > Add basic trace events for i2c_master_send() and i2c_master_recv() so we > > can observe the I2C activity without filling up the dmesg ring buffer. It > > also makes it easy to enable and disable tracing of the i2c-core. > This doesn't make sense. If you want to trace something, trace > i2c_transfer(). i2c_master_send() and i2c_master_recv() are only helpers > for the most simple cases, so tracing only them is pointless. > Note that even with this, you'll miss calls to i2c_smbus_xfer(), which > is the other access point to I2C/SMBus controllers. So I guess you want > to trace it as well. Might also be interesting to do start/stop tracing - I2C is relatively slow and causes scheduling. Dunno if it's worth it, though you could always turn on only one of the events if it was too boring to have both. -- 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
