From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751661AbbCTHpF (ORCPT ); Fri, 20 Mar 2015 03:45:05 -0400 Received: from metis.ext.pengutronix.de ([92.198.50.35]:51368 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751258AbbCTHpD (ORCPT ); Fri, 20 Mar 2015 03:45:03 -0400 Date: Fri, 20 Mar 2015 08:44:47 +0100 From: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= To: Wolfram Sang Cc: linux-i2c@vger.kernel.org, linux-sh@vger.kernel.org, Magnus Damm , Simon Horman , Laurent Pinchart , Geert Uytterhoeven , Andrey Danin , Marc Dietrich , Debora Grosse , linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/3] i2c: slave: rework the slave API Message-ID: <20150320074447.GE10068@pengutronix.de> References: <1426164123-8853-1-git-send-email-wsa@the-dreams.de> <1426164123-8853-2-git-send-email-wsa@the-dreams.de> <20150319201751.GZ10068@pengutronix.de> <20150320071504.GA906@katana> <20150320072441.GA10068@pengutronix.de> <20150320073135.GC906@katana> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20150320073135.GC906@katana> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: 2001:67c:670:100:1d::c0 X-SA-Exim-Mail-From: ukl@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 20, 2015 at 08:31:35AM +0100, Wolfram Sang wrote: > > > > > > After more discussion, brave users, and additional datasheet evaluation, > > > > > some API updates for the new I2C slave framework became imminent. The > > > > > slave events now get some easier to understand naming. Also, the event > > > > > handling has been simplified to only send one event per interrupt. > > > > what is an interrupt here? An event where the bus driver needs feedback > > > > from the backend? > > > > > > More the other way around: when the bus driver needs to notify the > > > backend. I wasn't 100% sure about the word 'interrupt', but then decided > > > a HW slave support without interrupts would be so rare and adventurous > > > that it is okay to use the term :) > > Yeah, I agree on HW slave support without interrupts is hardly possible. > > But I imagine that controllers differ in which situations they can issue > > an interrupt so talking about them for generic code feels strange to me > > because $flexiblecontrolerwithvariousirqs doesn't need to send more > > events than $bareminimumcontroler. > > Do you have a better word at hand? "...to send one event per event"? :) Maybe: Also, the event handling has been simplified to only need a single call to the slave callback when an action by the backend is required. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | http://www.pengutronix.de/ |