From mboxrd@z Thu Jan 1 00:00:00 1970 From: Trent Piepho Subject: Re: i2c device does not support repeated start Date: Wed, 14 May 2008 11:22:46 -0700 (PDT) Message-ID: References: <20080514122528.75924c09@hyperion.delvare> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20080514122528.75924c09-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: i2c-bounces-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org Errors-To: i2c-bounces-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org To: Jean Delvare Cc: Darius , i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org List-Id: linux-i2c@vger.kernel.org On Wed, 14 May 2008, Jean Delvare wrote: > Hi Darius, > > On Wed, 14 May 2008 12:55:09 +0300, Darius wrote: > > If device does not support that, maybe there is some special flag, which > > device driver can pass to i2c_master_xfer? > > No, there isn't. If a given I2C device doesn't support repeated start, > then its driver should simply run only single-message transactions. > That is, only use i2c_master_send() and i2c_master_recv(), or for SMBus > compatibility, i2c_smbus_read_byte() and i2c_smbus_write_*(). There is also a flag, I2C_M_NOSTART, that can keep the repeated start from being sent. Though this is probably not what you want, as you probably want to insert a stop instead of remove the start. _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c