From mboxrd@z Thu Jan 1 00:00:00 1970 From: Esben Haabendal Subject: Re: [PATCH v2] i2c-mpc: generate START condition after STOP caused by read i2c_msg Date: Tue, 26 May 2009 13:30:21 +0200 Message-ID: References: <4A124202.4010201@doredevelopment.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4A124202.4010201@doredevelopment.dk> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linuxppc-dev-bounces+glppe-linuxppc-embedded-2=m.gmane.org@ozlabs.org Errors-To: linuxppc-dev-bounces+glppe-linuxppc-embedded-2=m.gmane.org@ozlabs.org To: Esben Haabendal Cc: linuxppc-dev@ozlabs.org, linux-i2c@vger.kernel.org List-Id: linux-i2c@vger.kernel.org On Tue, May 19, 2009 at 7:22 AM, Esben Haabendal w= rote: > This fixes MAL (arbitration lost) bug caused by illegal use of > RSTA (repeated START) after STOP condition generated after last byte > of reads. With this patch, it is possible to do an i2c_transfer() with > additional i2c_msg's following the I2C_M_RD messages. > > It still needs to be resolved if it is possible to fix this issue > by removing the STOP condition after reads in a robust way. > > Signed-off-by: Esben Haabendal > --- > =A0drivers/i2c/busses/i2c-mpc.c | =A0 =A09 +++++++-- > =A01 files changed, 7 insertions(+), 2 deletions(-) Any blockers to get this accepted? /Esben