[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140912085836.GS3755@pengutronix.de>
Date: Fri, 12 Sep 2014 10:58:36 +0200
From: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
To: Wolfram Sang <wsa@...-dreams.de>
Cc: linux-i2c@...r.kernel.org, Jean Delvare <jdelvare@...e.de>,
Magnus Damm <magnus.damm@...il.com>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-sh@...r.kernel.org
Subject: Re: [RFC 0/4] i2c: slave support framework for Linux devices
Hello Wolfram,
On Tue, Sep 09, 2014 at 04:54:26PM +0200, Wolfram Sang wrote:
> 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/
>
> 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.
Some thoughts from reading through your patch set:
- If I understand correctly you cannot register an i2c slave without
also registering a master, right? I don't think this is troubling in
practice, is it?
For abstraction I would prefer to make these different concepts
though.
- The IMHO most (even only?) useful slave is "i2cslvdev", i.e. a
userspace device. With that you wouldn't need device tree stuff, the
driver would just offer the device if supported. Userspace then could
care about the rest (slave address, functionality, ...).
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
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