From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754732AbaIKMGQ (ORCPT ); Thu, 11 Sep 2014 08:06:16 -0400 Received: from mout.gmx.net ([212.227.17.22]:52679 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754568AbaIKMGO (ORCPT ); Thu, 11 Sep 2014 08:06:14 -0400 From: Marc Dietrich To: Wolfram Sang Cc: linux-i2c@vger.kernel.org, linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Jean Delvare , Magnus Damm , Andrey Danin Subject: Re: [RFC 0/4] i2c: slave support framework for Linux devices Date: Thu, 11 Sep 2014 14:06:06 +0200 Message-ID: <5110809.ZO3zEWmmzZ@fb07-iapwap2> User-Agent: KMail/4.13.3 (Linux/3.16.1-46.g90bc0f1-desktop; KDE/4.13.3; x86_64; ; ) In-Reply-To: <1410274470-12712-1-git-send-email-wsa@the-dreams.de> References: <1410274470-12712-1-git-send-email-wsa@the-dreams.de> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="ISO-8859-1" X-Provags-ID: V03:K0:PJ/ij8LwUqll7FYEijfbUKwT8na379nVSQTL3MlGY9nkM0oO9Mp kaEOdHcBX8JVvZ7X+LIuJRR3oRbUXVn2tV1bzwDsTUnQnNLLm73vC5SAXFBy5iadHrAX7VS cPTXMP4AivCX/5ms00IDJ5xv36o8DiYEvDVJo72lesyxHtRzVjXqXathf1ZrQvHsmCbUrth ziPTR8oKbNlG9DK4meOag== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Wolfram, Am Dienstag, 9. September 2014, 16:54:26 schrieb Wolfram Sang: > Finally, here is my take on the often desired feature that Linux can not > only be an I2C master, but also an I2C slave. Compared to my draft sent out > last week, this RFC has been tested on hardware (Renesas Lager board) and > works \o/ first, thanks for taking up this job. > One big part still missing is documentation, so brave ones need to "use the > source". However, this approach turned out to be even less intrusive than > expected, so that is hopefully a good sign. > > Basically, an I2C slave is a standard I2C client providing a callback > function. When registering as a slave, the connection to the I2C adapter is > made which uses the callback when a slave event happens. That splits the HW > support (enabling slave mode on the adapter) and SW support (here a generic > eeprom simulator) nicely IMO. >>From what I can tell, this approach may also work with our driver (staging/nvec). I especially like the split between the adapter and the client support. I only have one question so far regarding the device tree representation attached patch 4. Marc