From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: SMDK6440: I2C writes fails Date: Thu, 24 Jun 2010 12:32:36 +0100 Message-ID: <20100624113236.GA3958@opensource.wolfsonmicro.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from opensource.wolfsonmicro.com ([80.75.67.52]:51401 "EHLO opensource2.wolfsonmicro.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754706Ab0FXLci (ORCPT ); Thu, 24 Jun 2010 07:32:38 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-samsung-soc-owner@vger.kernel.org List-Id: linux-samsung-soc@vger.kernel.org To: Naveen Krishna Ch Cc: linux-samsung-soc@vger.kernel.org, Ben Dooks On Wed, Jun 23, 2010 at 11:15:55AM +0530, Naveen Krishna Ch wrote: > Where should i be looking, I would suggest looking at the driver and comparing it with the datasheet. > Will changing the spin counts work? I'd expect this to be unlikely. Note that if we run out of spins we still go for the 1ms sleep that was being used originally so it's more likely that there's a bug in the chip when that register is being read (though this would be surprising) or some other change in your kernel is causing problems.