On Tue, Jan 03, 2017 at 10:29:34PM +0100, Benjamin Tissoires wrote: > On Jan 03 2017 or thereabouts, Dmitry Torokhov wrote: > > > Yet another option: can we add a new flag to i2c_board_info controlling > > whether we want to enable/disable wiring up host notify interrupt? > > That should be fairly easy to implement. For now, given that only Elan > and Synaptics are the one in need for Host Notify, it could be better to > request the Host Notify IRQ instead of disabling it unconditionally > (which would make the current yet 8 years old lis3lv02d driver happy > again). I like that we have it done in i2c core instead of having drivers implementing it individually. Since you are saying that handling host notify is property of the slave/driver maybe we should be adding a flag to the *i2c_driver* structure to let i2c core that we want to have host notify mapped as interrupt if "native" interrupt is not supplied by the platform code? Thanks. -- Dmitry -- 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
