From: Kevin Hilman <khilman@baylibre.com>
To: Andreas Kemnade <andreas@kemnade.info>,
Jonathan Cameron <jic23@kernel.org>
Cc: akemnade@kernel.org,
"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>,
"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: Wed, 14 Jan 2026 14:30:02 -0800 [thread overview]
Message-ID: <7ha4yfzv2t.fsf@baylibre.com> (raw)
In-Reply-To: <20260112094259.4648cfaa@kemnade.info>
Andreas Kemnade <andreas@kemnade.info> writes:
> On Sun, 11 Jan 2026 12:32:00 +0000
> Jonathan Cameron <jic23@kernel.org> wrote:
>
>> 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.
>>
> well, it needs things fixed via patch 1 to avoid creating havoc...
> But from a strictly dogmatic point of view the devicetree describes the
> hardware, so it is unrelated.
> ... but from a more pragmatic point of view, I do not want to have interrupts
> enabled for drivers which do not handle them correctly.
>
> Of course this should be picked up by omap folks.
Based on the changelog comments, I will pick up the DT patch when the
driver fix gets applied.
Kevin
next prev parent reply other threads:[~2026-01-14 22:30 UTC|newest]
Thread overview: 12+ 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
2026-01-12 8:42 ` Andreas Kemnade
2026-01-14 22:30 ` Kevin Hilman [this message]
2026-05-06 12:20 ` Andreas Kemnade
2026-05-06 17:24 ` Kevin Hilman
2026-05-06 17:24 ` (subset) [PATCH 0/2] iio: imu: inv-mpu9150: fix interrupts for MPU9150 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=7ha4yfzv2t.fsf@baylibre.com \
--to=khilman@baylibre.com \
--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=jic23@kernel.org \
--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 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.