From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: omapfb: help from userspace Date: Thu, 16 Oct 2008 15:52:23 -0700 Message-ID: <20081016225222.GA15820@atomide.com> References: <13B9B4C6EF24D648824FF11BE89671620365B58844@dlee02.ent.ti.com> <20081009124357.GF26230@atomide.com> <20081016205743.GS15820@atomide.com> <20081016221053.GZ15820@atomide.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="xesSdrSSBC0PokLI" Return-path: Received: from mho-01-bos.mailhop.org ([63.208.196.178]:59783 "EHLO mho-01-bos.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754996AbYJPWw1 (ORCPT ); Thu, 16 Oct 2008 18:52:27 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Nathan Monson Cc: Paul Walmsley , "Woodruff, Richard" , "linux-omap@vger.kernel.org List" , "TK, Pratheesh Gangadhar" , Rick Bronson --xesSdrSSBC0PokLI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline * Nathan Monson [081016 15:15]: > On Thu, Oct 16, 2008 at 3:10 PM, Tony Lindgren wrote: > > No.. And I also got some -33 errors here too :( So back to the drawing > > board. > > > > Could you post step by step instructions on how you can reproduce your > > problem? > > I'm running the DSP Bridge patches in my kernel. I got them set up > using this guide: > http://elinux.org/BeagleBoard/DSP_Howto > > That guide also points to some sample binaries, including 'ping.out', > which is a simple round-trip test between the DSP and ARM. > > To reproduce, I do this: > 1) Boot kernel with mem=122m > 2) modprobe bridgedriver phys_mempool_base=0x87a00000 > phys_mempool_size=0x600000 > base_img=/home/root/dsp/ddspbase_tiomap3430.dof64P > 3) while true; do ./ping.out; done > > This ALWAYS reproduces within seconds. > > If the DSP patches are too much work to get set up, I've also heard > that people can reproduce this issue by playing movie files with > mplayer on Angstrom. Thanks, I'll set that up when I get a chance. Meanwhile, here's one more patch for you to test if you have a chance. Maybe also do a power off for few seconds before booting with this just in case. If this still does not help, then we'll use the strongly ordered patch for now, and tag v2.6.27-omap1 tomorrow. Then we can continue debugging the issue until we fully understand it. Tony --xesSdrSSBC0PokLI Content-Type: text/x-diff; charset=us-ascii Content-Disposition: inline; filename="intc-write-readback.patch" --- a/arch/arm/mach-omap2/irq.c +++ b/arch/arm/mach-omap2/irq.c @@ -53,6 +53,7 @@ static struct omap_irq_bank { static void intc_bank_write_reg(u32 val, struct omap_irq_bank *bank, u16 reg) { __raw_writel(val, bank->base_reg + reg); + __raw_readl(bank->base_reg + reg); } static u32 intc_bank_read_reg(struct omap_irq_bank *bank, u16 reg) --xesSdrSSBC0PokLI--