[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aFj__w2rf4UEJvhY@smile.fi.intel.com>
Date: Mon, 23 Jun 2025 10:19:27 +0300
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Marek Vasut <marek.vasut@...lbox.org>
Cc: Andy Shevchenko <andy.shevchenko@...il.com>,
Marek Vasut <marek.vasut+bmc150@...lbox.org>,
Hans de Goede <hansg@...nel.org>, linux-iio@...r.kernel.org,
Nuno Sá <nuno.sa@...log.com>,
Andy Shevchenko <andy@...nel.org>,
David Lechner <dlechner@...libre.com>,
Jonathan Cameron <jic23@...nel.org>,
Julien Stephan <jstephan@...libre.com>,
Peter Zijlstra <peterz@...radead.org>,
Salvatore Bonaccorso <carnil@...ian.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] iio: accel: bmc150: Do not configure IRQ registers if no
IRQ connected
On Sat, Jun 21, 2025 at 07:33:41PM +0200, Marek Vasut wrote:
> On 6/16/25 1:09 PM, Andy Shevchenko wrote:
> > > > You can try to monitor the /sys/kernel/debug/pinctrl/*/pins files for any
> > > > changes that might happen on the sensor events. It might (help to) reveal
> > > > the IRQ line.
> > > Sooo ... if the IRQ line is not described in ACPI, it could still be
> > > connected ? Hum, I'll try to shake the laptop next time I power it up.
> >
> > Yes, it's possible, unfortunately due to the closed / per-product
> > nature of the Windows drivers.
>
> This is the only pins I got out of this, and there doesn't seem to be
> anything changing if I shake the machine:
Yeah, it's kinda hard to catch in case it's an edge triggered interrupt.
But for level shouldn't be that hard and it seems there is no luck so
far. :-(
That said, the best workaround now is what Hans suggested.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists