Afzal, Thanks! This set looks very interesting. As I've been chasing this bug all week, I haven't had time to sync our build up to the latest tree. So I'm still back at 3.4-rc6, and cannot directly patch this in a give it a try yet. However, I'll certainly take a look as soon as I can. My research on the issue so far has indicated that we may have a hardware issue not a software issue. We're seeing some nasty transients pouring in from our power supply. So, we're chasing that first. Thanks again for the post and suggestions though. I do want to get up to the 3.5 series as soon as I can. Best regards! ----- Original Message ----- From: "Mohammed, Afzal" <afzal@xxxxxx> To: CF Adad <cfadad@xxxxxxxxxxxxxx> Cc: "linux-omap@xxxxxxxxxxxxxxx" <linux-omap@xxxxxxxxxxxxxxx>; Tony Lindgren <tony@xxxxxxxxxxx>; "Shilimkar, Santosh" <santosh.shilimkar@xxxxxx> Sent: Tuesday, June 12, 2012 7:14 AM Subject: RE: Please help! AM35xx mm/slab.c BUG Hi, On Fri, Jun 08, 2012 at 01:20:13, CF Adad wrote: > Thanks for your thoughts! I may try fiddling a bit just to see if that helps. 5 series of patches for gpmc modifications [1-5] has been posted, In case it helps in resolving your issue, please let me know. You will have to use the new interface to make use of runtime calculation of smsc911x timing, [5.x] can be referred for how to do board modifications for smsc911x (please comment out any other gpmc peripheral initialization in your board code, seems you have nand, comment out nand initialization, even nand can be made to work with new changes, but avoiding it will probably reduce your burden) As your eth is 9221, either you can provide the timings based on it from board file or apply [6] over [1-5] (base: 3.5-rc1) Regards Afzal [1] http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg69501.html [2] http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg69881.html [3] http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg69891.html [4] http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg69897.html [5] http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg69917.html [5.x] http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg69924.html [6] diff --git a/arch/arm/mach-omap2/gpmc-smsc911x.c b/arch/arm/mach-omap2/gpmc-smsc911x.c index 4bfe721..34816b9 100644 --- a/arch/arm/mach-omap2/gpmc-smsc911x.c +++ b/arch/arm/mach-omap2/gpmc-smsc911x.c @@ -105,12 +105,12 @@ static void gpmc_smsc911x_timing(struct gpmc_time_ctrl *time_ctrl, { struct gpmc_timings t; /* SMSC 9220 timings */ - unsigned tcycle_r = 165; + unsigned tcycle_r = 45; unsigned tcsl_r = 32; unsigned tcsh_r = 133; unsigned tcsdv_r = 30; unsigned tdoff_r = 9; - unsigned tcycle_w = 165; + unsigned tcycle_w = 45; unsigned tcsl_w = 32; unsigned tcsh_w = 133; unsigned tdsu_w = 7; -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
