From: balbi@ti.com (Felipe Balbi) Date: Fri, 17 Sep 2010 13:41:33 +0300 Subject: [PATCH 14/14] omap4: Fix bootup crash observed with higher CPU clocks In-Reply-To: References: <1284716878-27667-10-git-send-email-santosh.shilimkar@ti.com> <1284716878-27667-11-git-send-email-santosh.shilimkar@ti.com> <1284716878-27667-12-git-send-email-santosh.shilimkar@ti.com> <1284716878-27667-13-git-send-email-santosh.shilimkar@ti.com> <1284716878-27667-14-git-send-email-santosh.shilimkar@ti.com> <1284716878-27667-15-git-send-email-santosh.shilimkar@ti.com> <7A436F7769CA33409C6B44B358BFFF0C014F13A77C@dlee02.ent.ti.com> <7A436F7769CA33409C6B44B358BFFF0C014F13A782@dlee02.ent.ti.com> Message-ID: <20100917104133.GP26474@legolas.emea.dhcp.ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org hi, On Fri, Sep 17, 2010 at 05:30:30AM -0500, Shilimkar, Santosh wrote: >Second your thought. Infact I wasn't ok to push this patch to start >with but it's needed till the timer hwmod gets merged to me, it just looks like "omap_test_timeout()" is timing out and that function is omap_dm_timer_set_source() is returning with a still-disabled clock. could you check if you get "cm: Module associated with clock gpt didn't enabled in 100000 tries" message on your dmesg ?? -- balbi