From: Marek Vasut <marek.vasut@mailbox.org>
To: Hans de Goede <hansg@kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Linus Walleij <linusw@kernel.org>
Cc: linux-iio@vger.kernel.org, "Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"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: Thu, 8 Jan 2026 22:55:30 +0100 [thread overview]
Message-ID: <7d327efe-94ce-458a-9394-eb5582f1c263@mailbox.org> (raw)
In-Reply-To: <c42243fd-ffd2-4144-875e-b156133eb031@kernel.org>
On 6/21/25 10:14 PM, Hans de Goede wrote:
Hello Hans,
> IIO has separate interfaces for exporting channels which can be polled by
> userspace and for triggers which is a more event driven interface.
>
> It should be possible to modify the driver to skip the trigger registration,
> while keeping the channels. E.g. iio-sensor-proxy will then automaticallt
> switch to polling in userspace.
I wonder if this got fixed by this commit in the meantime:
3aa385a9c75c ("iio: accel: bmc150: Fix irq assumption regression")
next prev parent reply other threads:[~2026-01-08 21:55 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
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 [this message]
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=7d327efe-94ce-458a-9394-eb5582f1c263@mailbox.org \
--to=marek.vasut@mailbox.org \
--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=linusw@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox