On Wed, Jan 04, 2017 at 08:57:22PM -0800, Dmitry Torokhov wrote: > Falling back unconditionally to HostNotify as primary client's interrupt > breaks some drivers which alter their functionality depending on whether > interrupt is present or not, so let's introduce a board flag telling I2C > core explicitly if we want wired interrupt or HostNotify-based one: > I2C_CLIENT_HOST_NOTIFY. > > For DT-based systems we introduce "host-notify" property that we convert > to I2C_CLIENT_HOST_NOTIFY board flag. > > Tested-by: Benjamin Tissoires <benjamin.tissoires@xxxxxxxxxx> > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx> > --- > > v1->v2: > > - of_read_property_bool -> of_property_read_bool > - did not change binding wording to avoit mentioning I2C core because we > use the same wording (mentioning I2C core) for wired interrupts > > Documentation/devicetree/bindings/i2c/i2c.txt | 8 ++++++++ Acked-by: Rob Herring <robh@xxxxxxxxxx> > drivers/i2c/i2c-core.c | 17 ++++++++--------- > include/linux/i2c.h | 1 + > 3 files changed, 17 insertions(+), 9 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
