All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Marek Vasut <marek.vasut@mailbox.org>
Cc: "Andy Shevchenko" <andy.shevchenko@gmail.com>,
	"Marek Vasut" <marek.vasut+bmc150@mailbox.org>,
	"Hans de Goede" <hansg@kernel.org>,
	linux-iio@vger.kernel.org, "Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"Julien Stephan" <jstephan@baylibre.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Salvatore Bonaccorso" <carnil@debian.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: accel: bmc150: Do not configure IRQ registers if no IRQ connected
Date: Mon, 23 Jun 2025 10:19:27 +0300	[thread overview]
Message-ID: <aFj__w2rf4UEJvhY@smile.fi.intel.com> (raw)
In-Reply-To: <3e7daf0d-6472-4e53-86eb-e5c5c1fd3640@mailbox.org>

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



  reply	other threads:[~2025-06-23  7:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13 12:45 [PATCH] iio: accel: bmc150: Do not configure IRQ registers if no IRQ connected Marek Vasut
2025-06-13 15:03 ` David Lechner
2025-06-13 15:09   ` Andy Shevchenko
2025-06-13 15:09 ` Andy Shevchenko
2025-06-13 17:02   ` Marek Vasut
2025-06-14 13:03     ` Jonathan Cameron
2025-06-16  8:47     ` Andy Shevchenko
2025-06-16 11:03       ` Marek Vasut
2025-06-16 11:09         ` Andy Shevchenko
2025-06-21 17:33           ` Marek Vasut
2025-06-23  7:19             ` Andy Shevchenko [this message]
2025-06-16 12:42 ` Hans de Goede
2025-06-21 17:17   ` Jonathan Cameron
2025-06-21 17:24     ` Marek Vasut
2025-06-21 20:14       ` Hans de Goede
2026-01-08 21:55         ` Marek Vasut
2026-01-09  9:24           ` Linus Walleij
2026-01-09 15:00             ` Marek Vasut
2025-07-22  8:55   ` Uwe Kleine-König
2025-07-22 14:48     ` Marek Vasut
2025-07-23 15:19       ` Andy Shevchenko
2025-10-01 18:25         ` Salvatore Bonaccorso
2025-11-15 18:23           ` Jonathan Cameron
2025-07-24 13:41     ` Jonathan Cameron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aFj__w2rf4UEJvhY@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=andy@kernel.org \
    --cc=carnil@debian.org \
    --cc=dlechner@baylibre.com \
    --cc=hansg@kernel.org \
    --cc=jic23@kernel.org \
    --cc=jstephan@baylibre.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marek.vasut+bmc150@mailbox.org \
    --cc=marek.vasut@mailbox.org \
    --cc=nuno.sa@analog.com \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.