From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dirk Behme Subject: Re: [beagleboard] Re: TWL4030 intermittent freakout on boot Date: Fri, 09 May 2008 20:08:34 +0200 Message-ID: <48249322.4060004@googlemail.com> References: <20080508182807.GE24454@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from fg-out-1718.google.com ([72.14.220.159]:13178 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750774AbYEISIL (ORCPT ); Fri, 9 May 2008 14:08:11 -0400 Received: by fg-out-1718.google.com with SMTP id 19so910456fgg.17 for ; Fri, 09 May 2008 11:08:09 -0700 (PDT) In-Reply-To: <20080508182807.GE24454@atomide.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: beagleboard@googlegroups.com, Koen Kooi , linux-omap@vger.kernel.org Cc: Paul Walmsley , felipe.balbi@nokia.com, peter.de-schrijver@nokia.com, Tony Lindgren Tony Lindgren wrote: > * Koen Kooi [080508 11:22]: > >>Op 8 mei 2008, om 20:13 heeft Paul Walmsley het volgende geschreven: >> >>>Hello everyone, >>> >>>occasionally the TWL4030 driver on the 3430SDP freaks out on boot. >>>(This >>>is either an ES2.0 or ES2.1, not sure.) Here's a partial console >>>log with >>>initcall debugging enabled. This probably happens every thirty or >>>forty >>>boots, I would guess. The board does boot to userspace when this >>>happens. >>> >>>Perhaps the TWL4030 experts out there might know what's going on? >>> >>><3>i2c_omap i2c_omap.1: controller timed out >>><3>i2c_omap i2c_omap.1: controller timed out >>><3>twl4030_usb: i2c write failed, line 422 >> >>Looks suspiciously like the symptons in >> >>http://code.google.com/p/beagleboard/issues/detail?id=14 > > > This also looks similar to the earlier twl4030 hangs where access > to some domains caused twl4030 to hang. If twl4030 hangs, there's > no way to reset it as all control is over I2C. When twl4030 hangs, > bootloader won't be able to detect the chip either unless devices > is power cycled (and USB cable detached). > > The reason earlier was that twl4030 internal clock was not being > programmed properly, and was fixed by patch > 0d81cf7e804c529c58d3054c1b9bdb7b3f1dec5d. Link for this is http://source.mvista.com/git/?p=linux-omap-2.6.git;a=commitdiff;h=0d81cf7e804c529c58d3054c1b9bdb7b3f1dec5d I don't know OMAP3 good enough yet, but which clock should we use on OMAP3 here? Does it make sense to use osc_ck for OMAP3 instead of osc_sys_ck, too? E.g something like ... if (cpu_is_omap2430() || cpu_is_omap34xx()) osc = clk_get(NULL, "osc_ck"); else osc = clk_get(NULL, "osc_sys_ck"); ... Dirk