From: Stephen Warren <swarren@wwwdotorg.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org,
Lee Jones <lee@kernel.org>
Subject: Re: [PATCH V2 4/7] clocksource: bcm2835: Migrate to new 'set-state' interface
Date: Mon, 15 Jun 2015 22:16:23 -0600 [thread overview]
Message-ID: <557FA317.3080607@wwwdotorg.org> (raw)
In-Reply-To: <20150616031757.GC26592@linux>
On 06/15/2015 09:17 PM, Viresh Kumar wrote:
> On 15-06-15, 20:57, Stephen Warren wrote:
>> On 06/12/2015 02:00 AM, Viresh Kumar wrote:
>>> Migrate bcm2835 driver to the new 'set-state' interface provided by
>>> the clockevents core, the earlier 'set-mode' interface is marked
>>> obsolete now.
>>>
>>> This also enables us to implement callbacks for new states of clockevent
>>> devices, for example: ONESHOT_STOPPED.
>>>
>>> We weren't doing anything in the ->set_mode() callback. So, this patch
>>> doesn't provide any set-state callbacks.
>>
>> This generates a panic at boot (on top of 4.1.0-rc8+, which certainly at
>> least booted fine):
>>
>>> [ 0.008586] clocksource timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns
>>> [ 0.018080] ------------[ cut here ]------------
>>> [ 0.022843] kernel BUG at kernel/time/clockevents.c:480!
>>> [ 0.028299] Internal error: Oops - BUG: 0 [#1] ARM
>>> [ 0.033237] CPU: 0 PID: 0 Comm: swapper Not tainted 4.1.0-rc8+ #46
>>> [ 0.039567] Hardware name: BCM2835
>>> [ 0.043092] task: c06fb648 ti: c06f6000 task.ti: c06f6000
>>> [ 0.048668] PC is at clockevents_register_device+0x15c/0x174
>
> This failed the sanity checks of clockevents core. Did you apply the
> first patch as well? Yes, its very much required.
>
> Also, there were dependencies on the latest tip, prepared for 4.2
> merge window and would have been better if you tested on top of that.
>
> But those dependencies are for some helpers which aren't used in this
> patch. So, it might work over rc8 + the first patch from this series..
>
> In case it doesn't, please test it over tip/master once.
I see. You didn't Cc me on patch 1, and didn't mention the dependency in
this patch. That usually means they're all independent, e.g. the same
change in n different drivers.
Anyway, I tracked down the whole series and applied it on top of
next-20150615 and everything seems OK (kernel boots, and UART, USB kbd &
SD card work), so this patch,
Tested-by: Stephen Warren <swarren@wwwdotorg.org>
next prev parent reply other threads:[~2015-06-16 4:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 8:00 [PATCH V2 0/7] clockevent: Migrate to new 'set-state' interface Viresh Kumar
2015-06-12 8:00 ` [PATCH V2 1/7] clockevents: Allow set-state callbacks to be optional Viresh Kumar
2015-06-29 8:47 ` Daniel Lezcano
2015-06-29 9:15 ` Thomas Gleixner
2015-06-12 8:00 ` [PATCH V2 2/7] clocksource: arm_arch_timer: Migrate to new 'set-state' interface Viresh Kumar
2015-06-12 8:00 ` [PATCH V2 3/7] clocksource: arm_global_timer: " Viresh Kumar
2015-06-12 8:22 ` Maxime Coquelin
2015-06-12 8:28 ` Viresh Kumar
2015-06-12 9:10 ` srini
2015-06-12 9:11 ` Viresh Kumar
2015-06-12 8:00 ` [PATCH V2 4/7] clocksource: bcm2835: " Viresh Kumar
2015-06-16 2:57 ` Stephen Warren
2015-06-16 3:17 ` Viresh Kumar
2015-06-16 4:16 ` Stephen Warren [this message]
2015-06-16 4:19 ` Viresh Kumar
2015-06-12 8:00 ` [PATCH V2 5/7] clocksource: bcm_kona: " Viresh Kumar
2015-06-12 8:00 ` [PATCH V2 6/7] clocksource: cs5535: " Viresh Kumar
2015-06-12 8:00 ` [PATCH V2 7/7] clocksource: em_sti: " Viresh Kumar
2015-06-18 9:10 ` [PATCH V2 0/7] clockevent: " Daniel Lezcano
2015-06-18 9:14 ` Daniel Lezcano
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=557FA317.3080607@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=daniel.lezcano@linaro.org \
--cc=lee@kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.org \
/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