From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Krishnamoorthy, Balaji T" Subject: Re: State of SDP4430 platform Date: Thu, 3 Mar 2011 20:53:38 +0530 Message-ID: References: <20110116010936.GA21795@n2100.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from na3sys009aog101.obsmtp.com ([74.125.149.67]:51797 "EHLO na3sys009aog101.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758190Ab1CCPXk (ORCPT ); Thu, 3 Mar 2011 10:23:40 -0500 Received: by vws11 with SMTP id 11so1261476vws.37 for ; Thu, 03 Mar 2011 07:23:38 -0800 (PST) In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Paul Walmsley Cc: Santosh Shilimkar , Russell King - ARM Linux , linux-omap@vger.kernel.org >> > > > in ES1, timeouts were observed only with RTC. >> > > > I2C burst access to IRQ registers and bq24156 were OK >> > > >> > > Was an errata generated for this bug? >> > >> > er, erratum, pardon me... >> >> Is an erratum present for this bug? >> >> Also, will you generate a patch for this to at least warn the user when >> this situation occurs? > > Still waiting for a response to this. Apologies for the delay Could only find Phoenix TWL6030 - ProDB00107890 for this errata This is not related to I2C module on OMAP4 so fixing in twl-core.c Description: I2C FS burst mode not functional Glitch in the I2C Data line when the I2C controller does a Burst Read Have tried to workaround by using single byte read for Phoenix ES1.0 http://www.mail-archive.com/linux-omap@vger.kernel.org/msg46054.html > > > - Paul >