From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Romain Naour <romain.naour@openwide.fr>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] s3c24xx with clocksource/clockevent (kernel 3.2.21)
Date: Sun, 21 Oct 2012 20:43:14 +0200 [thread overview]
Message-ID: <50844242.7010107@xenomai.org> (raw)
In-Reply-To: <50835162.5020401@openwide.fr>
On 10/21/2012 03:35 AM, Romain Naour wrote:
>> You mean the patch for the UART ? I can not take that patch. You have to
>> understand what goes wrong in the I-pipe core, or irq chip callbacks
>> implementation for this processor, and fix it there, not in the irq
>> handler for the serial interrupt.
> I think there is a problem when Linux unmask an IRQ line with
> irq_enable() and when there is an IRQ pending behind.
> I made some comments on the ipipe-tracer log
> (UART-samsung-bug-ipipe-tracer.txt)
Ok: first comment: thanks to this patch:
http://git.xenomai.org/?p=ipipe-gch.git;a=commitdiff;h=352ee07368a89133df74948f3dd71ae657c519a0;hp=5e7413789eb3d1ca1613e986cbeb6c979082a217
We know that irq_state_clr_masked is called when unmask_irq is called.
Second, to know why cond_unmask_irq does not unmask the irq, you can use
ipipe_trace_special to print the value of the various conditions.
It would have been better to include the relevant parts of the trace in
the mail body, this would have made answering simpler.
--
Gilles.
next prev parent reply other threads:[~2012-10-21 18:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 10:19 [Xenomai] s3c24xx with clocksource/clockevent (kernel 3.2.21) Romain Naour
2012-10-19 12:18 ` Gilles Chanteperdrix
2012-10-20 16:12 ` Romain Naour
2012-10-20 17:26 ` Gilles Chanteperdrix
2012-10-21 1:35 ` Romain Naour
2012-10-21 18:29 ` Gilles Chanteperdrix
2012-10-21 18:43 ` Gilles Chanteperdrix [this message]
2012-10-21 23:33 ` Romain Naour
2012-10-22 13:18 ` Gilles Chanteperdrix
2012-10-22 14:05 ` Gilles Chanteperdrix
2012-10-22 16:26 ` Romain Naour
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=50844242.7010107@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=romain.naour@openwide.fr \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.