On Thu, Jan 12, 2017 at 07:41:01PM +0100, Wolfram Sang wrote: > 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> > > Applied to for-current, thanks! > > How do we handle driver fixes? Shall I take them via I2C to have the > dependency clear? Or can they go seperately? The drivers that need this will go [hopefully] into next so they should be OK to go through my tree. -- Dmitry -- 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
