From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: David Kozub <zub@linux.fjfi.cvut.cz>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Kernel BUG in mfgpt_tick (cs5535-clockevt.c) on ALIX 2c3 - null call
Date: Thu, 12 Oct 2017 14:47:47 +0200 [thread overview]
Message-ID: <b73a4a2d-2820-8f44-aff3-07aaae823b00@linaro.org> (raw)
In-Reply-To: <alpine.LRH.2.21.1710112227110.21191@linux.fjfi.cvut.cz>
On 11/10/2017 22:48, David Kozub wrote:
[ ... ]
>>
>> + disable_timer(timer);
>> + cs5535_mfgpt_write(timer, MFGPT_REG_COUNTER, 0);
>> +
>> /* Set up the IRQ on the MFGPT side */
>> if (cs5535_mfgpt_setup_irq(timer, MFGPT_CMP2, &timer_irq)) {
>> printk(KERN_ERR DRV_NAME ": Could not set up IRQ %d\n",
>
> I tried that and the handler is still called. So I did some more random
> experiments and I found out that if I call disable_timer(timer) twice,
> then the issue is resolved (the handler is not called before the
> registration is finished.) And I don't have to set MFGPT_REG_COUNTER to 0.
Aha! we are close to a fix.
> I have no idea why do I have to call disable_timer twice.
For testing purpose, can you try by adding mmiowb() and/or wmb() after
disable_timer()?
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2017-10-12 12:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-07 21:26 David Kozub
2017-10-09 8:39 ` Daniel Lezcano
2017-10-09 19:33 ` David Kozub
2017-10-10 13:03 ` Daniel Lezcano
2017-10-10 21:19 ` David Kozub
2017-10-11 8:26 ` Daniel Lezcano
2017-10-11 20:48 ` David Kozub
2017-10-12 12:47 ` Daniel Lezcano [this message]
2017-10-12 15:29 ` Thomas Gleixner
2017-10-12 20:53 ` David Kozub
2017-10-16 9:30 ` Thomas Gleixner
2017-10-16 20:41 ` David Kozub
2017-10-18 18:23 ` Thomas Gleixner
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=b73a4a2d-2820-8f44-aff3-07aaae823b00@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=zub@linux.fjfi.cvut.cz \
/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
all inboxes | Powered by JetHome®