From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pali =?utf-8?B?Um9ow6Fy?= Subject: Re: [PATCH v2] i2c: do not enable fall back to Host Notify by default Date: Thu, 5 Jan 2017 13:39:00 +0100 Message-ID: <20170105123900.GE31083@pali> References: <20170105045722.GA17958@dtor-ws> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Content-Disposition: inline In-Reply-To: <20170105045722.GA17958@dtor-ws> Sender: linux-i2c-owner@vger.kernel.org To: Dmitry Torokhov Cc: Wolfram Sang , Rob Herring , Benjamin Tissoires , =?utf-8?B?TWljaGHFgiBLxJlwaWXFhA==?= , Jean Delvare , Takashi Iwai , linux-i2c@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: devicetree@vger.kernel.org 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 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 > Signed-off-by: Dmitry Torokhov Acked-by: Pali Rohár -- Pali Rohár pali.rohar@gmail.com