From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Subject: Re: I2C dummy adapter driver ? Date: Thu, 20 Feb 2014 09:49:48 -0700 Message-ID: <5306322C.8030703@wwwdotorg.org> References: <5305382E.9050902@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5305382E.9050902-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Sender: linux-i2c-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Sylwester Nawrocki , linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel Cc: Wolfram Sang List-Id: linux-i2c@vger.kernel.org On 02/19/2014 04:03 PM, Sylwester Nawrocki wrote: > Hi All, > > I was wondering whether it would be reasonable to create a generic > Linux dummy I2C bus controller driver. The rationale behind it is > there might be hardware configurations where I2C communication is > handled by firmware but still it is useful to have I2C slave devices ^^^^^^^^ That doesn't sound like a dummy driver. Rather, it sounds like a driver for the firmware(?) interface that's used to do the I2C transactions. > instantiated by a Linux I2C bus adapter driver. > It would be useful to have the common devicetree I2C binding scheme > working regardless of where the I2C communication is handled - in > firmware or by the host CPU. > > Currently we have a somewhat dummy I2C adapter driver at drivers/media/ > platform/exynos4-is/fimc-is-i2c.c. But it is going to be needed by > multiple SoCs and I thought about separating it or creating a generic > dummy I2C adapter driver. From mboxrd@z Thu Jan 1 00:00:00 1970 From: swarren@wwwdotorg.org (Stephen Warren) Date: Thu, 20 Feb 2014 09:49:48 -0700 Subject: I2C dummy adapter driver ? In-Reply-To: <5305382E.9050902@gmail.com> References: <5305382E.9050902@gmail.com> Message-ID: <5306322C.8030703@wwwdotorg.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 02/19/2014 04:03 PM, Sylwester Nawrocki wrote: > Hi All, > > I was wondering whether it would be reasonable to create a generic > Linux dummy I2C bus controller driver. The rationale behind it is > there might be hardware configurations where I2C communication is > handled by firmware but still it is useful to have I2C slave devices ^^^^^^^^ That doesn't sound like a dummy driver. Rather, it sounds like a driver for the firmware(?) interface that's used to do the I2C transactions. > instantiated by a Linux I2C bus adapter driver. > It would be useful to have the common devicetree I2C binding scheme > working regardless of where the I2C communication is handled - in > firmware or by the host CPU. > > Currently we have a somewhat dummy I2C adapter driver at drivers/media/ > platform/exynos4-is/fimc-is-i2c.c. But it is going to be needed by > multiple SoCs and I thought about separating it or creating a generic > dummy I2C adapter driver.