[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20260123080421._9VjDlE4@linutronix.de>
Date: Fri, 23 Jan 2026 09:04:21 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Stefan Klug <stefan.klug@...asonboard.com>
Cc: Xavier Roumegue <xavier.roumegue@....nxp.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Clark Williams <clrkwllms@...nel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-rt-devel@...ts.linux.dev,
Nicolas Dufresne <nicolas@...fresne.ca>
Subject: Re: [PATCH v2 3/3] media: dw100: Fix kernel oops with PREEMPT_RT
enabled
On 2026-01-22 15:44:58 [+0100], Stefan Klug wrote:
…
> There is one caveat though: During development regular "dw100
> 32e30000.dwe: Interrupt error: 0x1" errors occurred due to
> DW100_INTERRUPT_STATUS_INT_ERR_TIME_OUT being set. This only happened on
> non PREEMPT_RT setups when the interrupt handler was manually forced to
> be threaded. On PREEMPT_RT systems (where the interrupt handler is now
> implicitly threaded) this error was never seen.
This not something I would expect. If it is forced-threaded it is
forced-threaded on both (RT && !RT) so it should behave the same. It
might be related who it is handled (order wise) with the other (related)
interrupts in the system. Anyway. Removing that flag is the right flag
to do.
> Signed-off-by: Stefan Klug <stefan.klug@...asonboard.com>
Reviewed-by: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Sebastian
Powered by blists - more mailing lists