Re: [PATCH v2] i2c: do not enable fall back to Host Notify by default

2017-01-12 Thread Dmitry Torokhov
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

Re: [PATCH v2] i2c: do not enable fall back to Host Notify by default

2017-01-12 Thread Wolfram Sang
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 ex

Re: [PATCH v2] i2c: do not enable fall back to Host Notify by default

2017-01-09 Thread Rob Herring
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 ex

Re: [PATCH v2] i2c: do not enable fall back to Host Notify by default

2017-01-05 Thread Pali Rohár
On Wednesday 04 January 2017 20:57:22 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 explic