Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail

[Philippe Gerum <rpm@xenomai.org>]

François Legal <francois.legal@thom.fr.eu.org> writes:

> Le Mardi, Novembre 19, 2024 10:26 CET, Julien Aube <julien.aube@smile.fr> a écrit: 
>  
>> Hello,
>> 
>> Reading this exchange it reminds me of a problem I had a few months ago 
>> on the same platform.
>> 
>> Here is the thead :
>> 
>> https://lore.kernel.org/xenomai/6814fa90-015e-91df-6941-db643e4d4229@smile.fr/#r
>> 
>> 
>> Conclusion was that disabling the scutimer(*) on DTS level was enough to 
>> restore the correct usage and I did not found
>> any bad behaviour after that. The product has passed all the rt-test 
>> afterward.
>> 
>> 
>> (*)
>> &scutimer {
>>      /* scutimer is forced to disabled since it does not work with 
>> Xenomai */
>>      status = "disabled";
>> };
>> 
>> Maybe i'm completely off the subject, but maybe it's worth having a look ?
>> 
>> Julien
>> 
>> 
>
> Thanks. That fixes the problem. I'll dig into that driver to try to fix it and submit a patch then.
>

This may help:

diff --git a/arch/arm/kernel/smp_twd.c b/arch/arm/kernel/smp_twd.c
index 8377f1d030c3a..a28f6b7f7eabc 100644
--- a/arch/arm/kernel/smp_twd.c
+++ b/arch/arm/kernel/smp_twd.c
@@ -181,7 +181,7 @@ static irqreturn_t twd_handler(int irq, void *dev_id)
 {
 	struct clock_event_device *evt = dev_id;
 
-	if (twd_timer_ack()) {
+	if (!clockevent_is_oob(evt) || twd_timer_ack()) {
 		clockevents_handle_event(evt);
 		return IRQ_HANDLED;
 	}

-- 
Philippe.