On Tue, Jul 31, 2018 at 12:09 PM, Wolfram Sang <wsa@xxxxxxxxxxxxx> wrote: > >> After this happens we try to shutdown the PMIC that interact over I2C. >> I2C writes will need I2C interrupts to be enabled but in an interrupt >> disabled context if shutting PMIC is the last thing in the sequence >> which needs I2C writes is there an already existing solution to this >> scenario? Any pointers would help. > > No existing solution. Long standing, known problem. > > IIRC the latest design we discussed is to add a new callback to struct > i2c_algorithm like 'master_xfer_irqless' and teach the I2C core when to > call which callback. Which might not be so super straightforward because > for most drivers (except PMICs probably) using I2C when interrupts are > disabled is a bug and we also shouldn't hide that by providing a generic > fallback. Perhaps we should call it like i2c_pmic_xfer() to deliberately show that this is dedicated solely for PMICs? -- With Best Regards, Andy Shevchenko -- 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
