On 08/09/2012 11:37 PM, Shawn Guo wrote: > From: Richard Zhao <[email protected]> > > If CONFIG_SMP, cpufreq skips loops_per_jiffy update, because different > arch has different per-cpu loops_per_jiffy definition. > > Signed-off-by: Richard Zhao <[email protected]> > Acked-by: Russell King <[email protected]> > Acked-by: Santosh Shilimkar <[email protected]> > Signed-off-by: Shawn Guo <[email protected]>
I believe this patch is causing issues initializing PCI-Express on Tegra. In next-20120906, I cold-booted 10 times. 3 times, PCIe initialized OK, and 7 times, the driver timed out in arch/arm/mach-tegra/pcie.c function tegra_pcie_check_link(). With this patch reverted, another 10 cold boot attempts all succeeded just fine. Similarly, the regression appeared in next-20120905, and I isolated it to arch/arm/kernel/, and this is the only patch in that directory between next-20120904 and next-20120905. Do you have any idea what the problem might be? Looking at the timestamps in dmesg in the failing case, the driver is waiting the expected (per pcie.c driver code) 1.2 seconds before giving up on the port, although I suppose if the kernel's idea of real-time is off, then the dmesg log timestamps might be off too. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
