From: akemnade@kernel.org
To: "Jean-Baptiste Maneyrol" <jean-baptiste.maneyrol@tdk.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Aaro Koskinen" <aaro.koskinen@iki.fi>,
"Andreas Kemnade" <andreas@kemnade.info>,
"Kevin Hilman" <khilman@baylibre.com>,
"Roger Quadros" <rogerq@kernel.org>,
"Tony Lindgren" <tony@atomide.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
Andreas Kemnade <akemnade@kernel.org>
Subject: [PATCH 0/2] iio: imu: inv-mpu9150: fix interrupts for MPU9150
Date: Wed, 31 Dec 2025 22:14:15 +0100 [thread overview]
Message-ID: <20251231-mpu9150-v1-0-08ecf085c4ae@kernel.org> (raw)
The Epson Moverio BT200 has MPU9150 chips. The devicetree has a simple
typo regarding the interrupt of that chip. Simply fixing it unweils
problems in the driver causing IRQ storms by calling
iio_readdev -T 0 iio:deviceX
With the fix applied one IRQ comes per sampling when calling
iio_readdev -T 0 iio:deviceX which looks like sane behaviour.
Probably applying this series has to be split between different kernel
releases to avoid having fixed devicetree with broken driver.
Signed-off-by: Andreas Kemnade <akemnade@kernel.org>
---
Andreas Kemnade (2):
iio: imu: inv-mpu9150: fix irq ack preventing irq storms
ARM: dts: ti/omap: omap4-epson-embt2ws: fix typo in iio device property
arch/arm/boot/dts/ti/omap/omap4-epson-embt2ws.dts | 4 ++--
drivers/iio/imu/inv_mpu6050/inv_mpu_core.c | 8 ++++++++
drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h | 2 ++
drivers/iio/imu/inv_mpu6050/inv_mpu_trigger.c | 5 ++++-
4 files changed, 16 insertions(+), 3 deletions(-)
---
base-commit: f8f9c1f4d0c7a64600e2ca312dec824a0bc2f1da
change-id: 20251231-mpu9150-0f261490d17e
Best regards,
--
Andreas Kemnade <akemnade@kernel.org>
next reply other threads:[~2025-12-31 21:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 21:14 akemnade [this message]
2025-12-31 21:14 ` [PATCH 1/2] iio: imu: inv-mpu9150: fix irq ack preventing irq storms akemnade
2026-01-11 12:30 ` Jonathan Cameron
2026-01-30 16:17 ` Jean-Baptiste Maneyrol
2026-01-31 18:43 ` Jonathan Cameron
2025-12-31 21:14 ` [PATCH 2/2] ARM: dts: ti/omap: omap4-epson-embt2ws: fix typo in iio device property akemnade
2026-01-11 12:32 ` Jonathan Cameron
2026-01-12 8:42 ` Andreas Kemnade
2026-01-14 22:30 ` Kevin Hilman
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=20251231-mpu9150-v1-0-08ecf085c4ae@kernel.org \
--to=akemnade@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=jic23@kernel.org \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=tony@atomide.com \
/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