On Mon, Dec 6, 2010 at 8:30 PM, Paul Walmsley <paul@xxxxxxxxx> wrote: > > Commit 4d17aeb1c5b2375769446d13012a98e6d265ec13 ("OMAP: I2C: split > device registration and convert OMAP2+ to omap_device") broke I2C on > OMAP1. ÂThe following messages appear at boot: > > i2c_omap i2c_omap.1: failure requesting irq 0 > i2c_omap: probe of i2c_omap.1 failed with error -22 > > Investigation revealed that a chunk of code is missing from the > original plat-omap/i2c.c file which configured the IRQ and base address > for the I2C block on OMAP1. ÂUpon adding this back, the OMAP1 I2C block > seems to initialize correctly. > > Thanks to Cory Maccarrone <darkstar6262@xxxxxxxxx> for reporting the bug, > and apologies for the breakage. > > Signed-off-by: Paul Walmsley <paul@xxxxxxxxx> > Cc: Cory Maccarrone <darkstar6262@xxxxxxxxx> > Cc: Janusz Krzysztofik <jkrzyszt@xxxxxxxxxxxx> I tested this on my Herald. Seems to do the job. Tested-by: Cory Maccarrone <darkstar6262@xxxxxxxxx> - Cory -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html