From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3 1/3] ARM: add cpufreq transiton notifier to adjust loops_per_jiffy for smp
Date: Fri, 07 Sep 2012 10:55:00 -0600 [thread overview]
Message-ID: <504A26E4.4070600@wwwdotorg.org> (raw)
In-Reply-To: <20120907025847.GI26709@S2101-09.ap.freescale.net>
On 09/06/2012 08:58 PM, Shawn Guo wrote:
> On Thu, Sep 06, 2012 at 04:35:25PM -0600, Stephen Warren wrote:
>> 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.
>
> Just for identifying the problem, can you test the following change to
> see if it fixes the failure.
Yes, that does solve the problem (well, with s/late_init/late_initcall/).
As you imply, that change wouldn't help if cpu-tegra.c was built as a
module. So, is this something you can work around in your patch?
Thanks for the quick response.
next prev parent reply other threads:[~2012-09-07 16:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 5:37 [PATCH v3 0/3] Add a generic cpufreq-cpu0 driver Shawn Guo
2012-08-10 5:37 ` [PATCH v3 1/3] ARM: add cpufreq transiton notifier to adjust loops_per_jiffy for smp Shawn Guo
2012-09-04 23:27 ` Rafael J. Wysocki
2012-09-06 22:35 ` Stephen Warren
2012-09-07 2:58 ` Shawn Guo
2012-09-07 16:55 ` Stephen Warren [this message]
2012-09-10 1:17 ` Shawn Guo
2012-09-10 17:17 ` Stephen Warren
2012-09-11 11:59 ` Prashant Gaikwad
2012-09-11 15:16 ` Stephen Warren
2012-08-10 5:37 ` [PATCH v3 2/3] PM / OPP: Initialize OPP table from device tree Shawn Guo
2012-08-16 21:05 ` Rafael J. Wysocki
2012-08-17 0:52 ` Shawn Guo
2012-08-17 1:53 ` Rob Herring
2012-09-04 23:27 ` Rafael J. Wysocki
2012-08-10 5:37 ` [PATCH v3 3/3] cpufreq: Add a generic cpufreq-cpu0 driver Shawn Guo
2012-09-04 23:18 ` Rafael J. Wysocki
2012-09-05 1:12 ` Shawn Guo
2012-09-05 4:53 ` AnilKumar, Chimata
2012-09-05 5:02 ` Shilimkar, Santosh
2012-09-05 13:38 ` Rafael J. Wysocki
2012-09-05 13:59 ` Shawn Guo
2012-09-05 20:18 ` Rafael J. Wysocki
2012-09-06 7:29 ` Shawn Guo
2012-09-06 19:59 ` Rafael J. Wysocki
2012-08-31 6:42 ` [PATCH v3 0/3] " Shawn Guo
2012-09-01 5:53 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=504A26E4.4070600@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox