Hi, When a clock driver is controlling a clock that is controlled over I2C / SPI, we need to perform a write on that bus to enable the clock. However, such busses often have their own clocks that must be enabled. Since all clock prepares are controlled under one large mutex this easily causes deadlock. The device is waiting for the I2C / SPI write to complete and the I2C / SPI driver is waiting for the clock prepare lock to be released so it can enable its own clock. I have had a bit of a search and it seems the only really advice kicking about is that all I2C / SPI drivers should leave the clock prepared all the time. Is that intended to be the long term solution, should I treat not leaving the clock prepared as a bug? Thanks, Charles -- 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
