Re: Clock usbhost_48m_fck didn't enable in 100000 tries and crash

Hi Tony and Rogers, thanks for the reply. I found this: (clock3xxx_data.c) static struct clk usbhost_48m_fck = { .name = "usbhost_48m_fck", .ops= _omap3430es2_dss_usbhost_wait, .parent = _48m_fck, .enable_reg =

Re: Clock usbhost_48m_fck didn't enable in 100000 tries and crash

Daniel, On 24/11/15 15:36, Daniel. wrote: > Hi Michael > > About this: > "Two bugs are fixed by this patch. First, OMAP hardware only supports > target CM_IDLEST register bits on ES2+ chips and beyond. ES1 chips > should not wait for these clocks to enable. So, split the appropriate >

Re: Clock usbhost_48m_fck didn't enable in 100000 tries and crash

Hi Michael, Thanks for the help, The clock_summary is not there but I found these files: $ pwd /sys/kernel/debug/clock/virt_26m_ck/osc_sys_ck/sys_ck/dpll4_ck/dpll4_m2_ck/dpll4_m2x2_ck/omap_96m_alwon_fck/cm_96m_fck/omap_48m_fck/usbhost_48m_fck $ cat flags 0x $ cat flags rate

Re: Clock usbhost_48m_fck didn't enable in 100000 tries and crash

Doing some printk mess I found that the usbhost_48m_fck is enabled. So my problem should be another thing: clock.c:omap2_dflt_clk_enable@193: usbhost_48m_fck enable_reg value 0x01 2015-11-23 18:10 GMT-02:00 Michael Trimarchi : > Hi > > Can you check if you have this

Re: Clock usbhost_48m_fck didn't enable in 100000 tries and crash

Hi Do you have /sys/kernel/debug/clk/clock_summary? Michael On Tue, Nov 24, 2015 at 7:50 PM, Daniel. wrote: > Doing some printk mess I found that the usbhost_48m_fck is enabled. So > my problem should be another thing: > > clock.c:omap2_dflt_clk_enable@193:

Re: Clock usbhost_48m_fck didn't enable in 100000 tries and crash

Hi Michael About this: "Two bugs are fixed by this patch. First, OMAP hardware only supports target CM_IDLEST register bits on ES2+ chips and beyond. ES1 chips should not wait for these clocks to enable. So, split the appropriate clocks into ES1 and ES2+ variants, so that kernels

Re: Clock usbhost_48m_fck didn't enable in 100000 tries and crash

Hi On Mon, Nov 23, 2015 at 8:05 PM, Daniel. wrote: > Hi Michael, > > It's a plain linux. I'm considering upgrading kernel as last option. > Variscite doesn't > support another kernel for this SoM so this would be a really hard > work. I'm looking > for a solution on this

Re: Clock usbhost_48m_fck didn't enable in 100000 tries and crash

Hi, Building as built-in doesn't solve my problem. The difference is that when compiled as module the dump shows up when I load it, and when is built-in the dump shows up at boot time. Also when built-in the problem seems to ocurr when device is reseted (on ehci_omap_stop) and the first stack

Re: Clock usbhost_48m_fck didn't enable in 100000 tries and crash

Hi Can you check if you have this patch in? commit 3c82e229f09a6acc8d24dc27c5e0e60b1d7161c2 Author: Paul Walmsley Date: Fri Jul 24 19:44:06 2009 -0600 OMAP3 clock: correct module IDLEST bits: SSI; DSS; USBHOST; HSOTGUSB Fix two bugs in the OMAP3 clock tree pertaining

Re: Clock usbhost_48m_fck didn't enable in 100000 tries and crash

I've already tried, it fails to apply. My tree is based on last commit from TI linux-omap3 (4f1fb3bea4cc381c76e8e439f8af393c1a698dfc) so I *think* that this is already applied (since come from the same tree). I will try to apply it by hand Thanks! Regards, 2015-11-23 18:10 GMT-02:00 Michael

Clock usbhost_48m_fck didn't enable in 100000 tries and crash

Hi every body! I'm running a (2.6.37) kernel based on linux-omap tree (http://arago-project.org/git/projects/?p=linux-omap3.git;a=summary). The board is a SoM from Variscite (var-som-am3517). I've compiled the ehci-hcd as a module. When I enable it I got this dump: http://pastebin.com/5idXXBBi

Re: Clock usbhost_48m_fck didn't enable in 100000 tries and crash

Hi Daniel On Mon, Nov 23, 2015 at 7:45 PM, Daniel. wrote: > Hi every body! > > I'm running a (2.6.37) kernel based on linux-omap tree > (http://arago-project.org/git/projects/?p=linux-omap3.git;a=summary). > The board is a SoM from Variscite (var-som-am3517). > > I've

Re: Clock usbhost_48m_fck didn't enable in 100000 tries and crash

Hi Michael, It's a plain linux. I'm considering upgrading kernel as last option. Variscite doesn't support another kernel for this SoM so this would be a really hard work. I'm looking for a solution on this kernel and mainly trying to understand why usbhost_48m_fck is not getting enabled. I'm