From: Stephen Boyd <sboyd@codeaurora.org>
To: Stehle Vincent-B46079 <B46079@freescale.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
John Stultz <john.stultz@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: next-20130627 breaks i.MX6 sabre sd UART console
Date: Fri, 28 Jun 2013 08:57:30 -0700 [thread overview]
Message-ID: <51CDB26A.9060500@codeaurora.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1306281403530.4013@ionos.tec.linutronix.de>
On 06/28/13 05:09, Thomas Gleixner wrote:
> On Thu, 27 Jun 2013, Stehle Vincent-B46079 wrote:
>
> Cc'ed Mark and Stephen.
>
>> FYI I remark that today's Linux next 'next-20130627' breaks i.MX6
>> sabre sd UART console with ARM config imx_v6_v7_defconfig.
>> This was working fine yesterday with 'next-20130626'.
>>
>> Bisecting gave me this commit:
>>
>> 064706514ec3fea740c2656e03c4f01f6a551ac4 clocksource: Add generic
>> dummy timer driver
>>
>> If I revert it I do indeed get the boot messages on the UART console
>> again, but the kernel then crashes in wm8962_probe(). So there is
>> more to find out...
Do you have debug_ll support to get some serial logs? Also could you try
booting with maxcpus=1 on the kernel commandline? And it would be useful
to have the output of /proc/timer_list if you have it from a working
device. I believe you have a per-cpu TWD timer and a global imx-gpt? Can
you try this patch? (sorry about the whitespace damage)
----8<-----
diff --git a/arch/arm/mach-imx/time.c b/arch/arm/mach-imx/time.c
index fea9131..f05f1f1 100644
--- a/arch/arm/mach-imx/time.c
+++ b/arch/arm/mach-imx/time.c
@@ -267,7 +267,7 @@ static int __init mxc_clockevent_init(struct clk *timer_clk)
if (timer_is_v2())
clockevent_mxc.set_next_event = v2_set_next_event;
- clockevent_mxc.cpumask = cpumask_of(0);
+ clockevent_mxc.cpumask = cpu_all_mask;
clockevents_config_and_register(&clockevent_mxc,
clk_get_rate(timer_clk),
0xff, 0xfffffffe);
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-06-28 15:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 18:49 next-20130627 breaks i.MX6 sabre sd UART console Stehle Vincent-B46079
2013-06-28 12:09 ` Thomas Gleixner
2013-06-28 15:57 ` Stephen Boyd [this message]
2013-06-28 16:58 ` Stehle Vincent-B46079
2013-06-28 17:06 ` Stephen Boyd
2013-06-29 2:07 ` Stephen Boyd
2013-07-01 10:04 ` Mark Rutland
2013-07-01 10:29 ` Stehle Vincent-B46079
2013-07-01 13:04 ` Thomas Gleixner
2013-07-01 13:22 ` Stehle Vincent-B46079
2013-07-01 17:49 ` Thomas Gleixner
2013-07-01 19:45 ` Stehle Vincent-B46079
2013-07-01 19:50 ` Stephen Boyd
2013-07-01 20:14 ` Thomas Gleixner
2013-07-01 20:54 ` Stephen Boyd
2013-07-01 21:24 ` Thomas Gleixner
2013-07-01 22:14 ` Stephen Boyd
2013-07-01 22:22 ` Thomas Gleixner
2013-07-02 7:18 ` Stehle Vincent-B46079
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=51CDB26A.9060500@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=B46079@freescale.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).