[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121207123343.GU14363@n2100.arm.linux.org.uk>
Date: Fri, 7 Dec 2012 12:33:43 +0000
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Tushar Behera <tushar.behera@...aro.org>
Cc: Giridhar Maruthy <giridhar.maruthy@...aro.org>,
linux-samsung-soc@...r.kernel.org, w.sang@...gutronix.de,
linux-kernel@...r.kernel.org, kgene.kim@...sung.com,
linux-i2c@...r.kernel.org, ben-linux@...ff.org, khali@...ux-fr.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] I2C: EXYNOS: Add slave support to i2c
On Fri, Dec 07, 2012 at 05:33:17PM +0530, Tushar Behera wrote:
> On 12/03/2012 05:46 PM, Giridhar Maruthy wrote:
> > This patch adds slave support to i2c. The dt entry i2c-mode
> > decides at probe time if the controller needs to work in
> > slave mode and the controller is accordingly programmed.
(I don't have the original patches.)
Hmm. How has slave-mode support been tested?
Remembering that I2C slave devices do not initiate bus accesses, all
accesses will be started by some other master. How are you dealing
with the bytes received from the master, and how are you returning a
response to the master in reply to a read request?
We had support for this on PXA I2C through a callback from the driver
into PXA code (used for the Psion Teklogix Netbook device) and it worked
really well, but what you can't do is use the standard I2C interfaces
for slave mode.
--
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