public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: marvin24@gmx.de (Marc Dietrich)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 0/4] i2c: slave support framework for Linux devices
Date: Thu, 11 Sep 2014 14:06:06 +0200	[thread overview]
Message-ID: <5110809.ZO3zEWmmzZ@fb07-iapwap2> (raw)
In-Reply-To: <1410274470-12712-1-git-send-email-wsa@the-dreams.de>

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

  parent reply	other threads:[~2014-09-11 12:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09 14:54 [RFC 0/4] i2c: slave support framework for Linux devices Wolfram Sang
2014-09-09 14:54 ` [RFC 1/4] i2c: core changes for slave support Wolfram Sang
2014-09-09 14:54 ` [RFC 2/4] i2c: slave: add eeprom simulator driver Wolfram Sang
2014-09-09 16:34   ` Wolfram Sang
2014-09-09 14:54 ` [RFC 3/4] i2c: rcar: add slave support Wolfram Sang
2014-09-09 14:54 ` [RFC 4/4] ARM: shmobile: r8a7790: adapt DTS for I2C " Wolfram Sang
2014-09-11 12:17   ` Marc Dietrich
2014-09-11 14:12     ` Wolfram Sang
2014-09-11 14:40       ` Wolfram Sang
2014-09-11 14:52         ` Marc Dietrich
2014-09-11 14:54           ` Wolfram Sang
2014-09-12  7:51             ` Marc Dietrich
2014-09-12  8:08               ` Geert Uytterhoeven
2014-09-12  8:33               ` Wolfram Sang
2014-09-12  9:06                 ` Marc Dietrich
2014-09-12  9:58                   ` Wolfram Sang
2014-09-12 10:10                     ` Geert Uytterhoeven
2014-09-12 10:26                       ` Wolfram Sang
2014-09-12 11:42                     ` Marc Dietrich
2014-09-12 12:15                       ` Wolfram Sang
2014-09-11 14:49       ` Marc Dietrich
2014-09-11 12:06 ` Marc Dietrich [this message]
2014-09-12  8:58 ` [RFC 0/4] i2c: slave support framework for Linux devices Uwe Kleine-König
2014-09-12  9:12   ` Wolfram Sang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5110809.ZO3zEWmmzZ@fb07-iapwap2 \
    --to=marvin24@gmx.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox