[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260203145856.Rc52LIS5@linutronix.de>
Date: Tue, 3 Feb 2026 15:58:56 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Bert Karwatzki <spasswolf@....de>
Cc: linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org,
Jiri Kosina <jikos@...nel.org>, Jonathan Cameron <jic23@...nel.org>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Thomas Gleixner <tglx@...nel.org>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>
Subject: Re: [tip: irq/core] genirq: Warn about using IRQF_ONESHOT without a
threaded handler
On 2026-02-03 11:43:53 [+0100], Bert Karwatzki wrote:
> Yes, this should call warn_no_thread() when the interrupt is triggered, but
> I don't know if these sensors are actually functional on my laptop (I've never
> tried to use them).
>
> So I installed libiio-utils from debian and this is the output from
> iio_info:
…
>
> The iio:device* sensors all report 0 for the "offset value", so these
> sensors are maybe non-fuctional.
>
>
> > What did I miss?
>
> I don't think you missed something, but the thread function being NULL here
> could a problem on devices where these sensors actually work. (Or perhaps these sensors
> need to be polled and the interrupts never trigger (?))
I only found one handler where the thread handler was NULL and it
returned WAKE_THREAD. So this _is_ broken.
Was it one of the driver I mentioned? If so I suggest to fix those
first. I have no idea how this should work…
> Bert Karwatzki
Sebastian
Powered by blists - more mailing lists