[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5110809.ZO3zEWmmzZ@fb07-iapwap2>
Date: Thu, 11 Sep 2014 14:06:06 +0200
From: Marc Dietrich <marvin24@....de>
To: Wolfram Sang <wsa@...-dreams.de>
Cc: linux-i2c@...r.kernel.org, linux-sh@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Jean Delvare <jdelvare@...e.de>,
Magnus Damm <magnus.damm@...il.com>,
Andrey Danin <danindrey@...l.ru>
Subject: Re: [RFC 0/4] i2c: slave support framework for Linux devices
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists