On Fri, May 18, 2012 at 11:52:06PM +0200, Wolfgang Denk wrote:
Dear Tom Rini,
In message 4FB69847.2090703@ti.com you wrote:
Right. I'm not suggesting removing i2c probe, I'm just suggesting making it opt-out'able. For example, on the beaglebone I can make i2c probe work as expected. It's just requring that we toggle the I2C_CON enable bit for some reason in probe, but not when we are actually trying to write to a bad address. I'd like to just #undef CONFIG_CMD_I2C_PROBE for the board and be done with it. Otherwise it lists (nearly) every address which is useless.
Can you use bit-banged I2C on these boards?
In this particular case it worked out to being that a previous change to the probe code violated the TRM, but didn't cause (obvious?) harm on older versions of the IP block but on newer ones (am33xx, omap4+) it does. I'll drop the idea of making i2c probe command opt-out.