From: Jonathan Cameron <jic23@kernel.org>
To: akemnade@kernel.org
Cc: "Jean-Baptiste Maneyrol" <jean-baptiste.maneyrol@tdk.com>,
"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>,
"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
Subject: Re: [PATCH 2/2] ARM: dts: ti/omap: omap4-epson-embt2ws: fix typo in iio device property
Date: Sun, 11 Jan 2026 12:32:00 +0000 [thread overview]
Message-ID: <20260111123200.6871a41b@jic23-huawei> (raw)
In-Reply-To: <20251231-mpu9150-v1-2-08ecf085c4ae@kernel.org>
On Wed, 31 Dec 2025 22:14:17 +0100
akemnade@kernel.org wrote:
> From: Andreas Kemnade <andreas@kemnade.info>
>
> Define interrupts properly. Unfortunately, this hides a bug in the linux
> driver, so it needs to be used with the driver fixed only.
>
> Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
Not related to patch 1 so if TI soc folk can pick this up that would be
great.
> ---
> arch/arm/boot/dts/ti/omap/omap4-epson-embt2ws.dts | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/ti/omap/omap4-epson-embt2ws.dts b/arch/arm/boot/dts/ti/omap/omap4-epson-embt2ws.dts
> index c90f43cc2fae9..a9f0cfd7c999d 100644
> --- a/arch/arm/boot/dts/ti/omap/omap4-epson-embt2ws.dts
> +++ b/arch/arm/boot/dts/ti/omap/omap4-epson-embt2ws.dts
> @@ -346,7 +346,7 @@ mpu9150h: imu@68 {
> pinctrl-names = "default";
> pinctrl-0 = <&mpu9150h_pins>;
> interrupt-parent = <&gpio2>;
> - interrupt = <19 IRQ_TYPE_LEVEL_HIGH>;
> + interrupts = <19 IRQ_TYPE_LEVEL_HIGH>;
> };
> };
>
> @@ -408,7 +408,7 @@ mpu9150: imu@68 {
> pinctrl-names = "default";
> pinctrl-0 = <&mpu9150_pins>;
> interrupt-parent = <&gpio2>;
> - interrupt = <7 IRQ_TYPE_LEVEL_HIGH>;
> + interrupts = <7 IRQ_TYPE_LEVEL_HIGH>;
> vddio-supply = <&cb_v18>;
> vdd-supply = <&cb_v33>;
> invensense,level-shifter;
>
next prev parent reply other threads:[~2026-01-11 12:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 21:14 [PATCH 0/2] iio: imu: inv-mpu9150: fix interrupts for MPU9150 akemnade
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 [this message]
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=20260111123200.6871a41b@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=aaro.koskinen@iki.fi \
--cc=akemnade@kernel.org \
--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=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