[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <28c6add2-311e-5638-e890-53a2248f560a@metafoo.de>
Date: Sun, 2 Aug 2020 17:05:51 +0200
From: Lars-Peter Clausen <lars@...afoo.de>
To: Jonathan Cameron <jic23@...nel.org>,
Christian Eggers <ceggers@...i.de>
Cc: stable@...r.kernel.org, Hartmut Knaack <knaack.h@....de>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] iio: trigger: sysfs: Disable irqs before calling
iio_trigger_poll()
On 8/1/20 6:02 PM, Jonathan Cameron wrote:
> On Mon, 27 Jul 2020 16:57:13 +0200
> Christian Eggers <ceggers@...i.de> wrote:
>
>> iio_trigger_poll() calls generic_handle_irq(). This function expects to
>> be run with local IRQs disabled.
> Was there an error or warning that lead to this patch?
> Or can you point to what call in generic_handle_irq is making the
> assumption that we are breaking?
>
> Given this is using the irq_work framework I'm wondering if this is
> a more general problem?
>
> Basically more info please!
There is this series https://lkml.org/lkml/2020/3/6/433 which causes
generic_handle_irq() to issue an warning if it is called with IRQs on,
for a IRQ controller that can't handle it.
But I'm not convinced this applies to the IIO code, since this is a
purely virtual interrupt and is not interfering with any interrupt
controller hardware.
Powered by blists - more mailing lists