From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Joe Sandom" <joe.g.sandom@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
martin.triska@mycroftmind.com,
"Jan Remes" <jan.remes@mycroftmind.com>
Subject: Re: [PATCH v2 0/4] iio: light: tsl2591: fix lux calculation and precision, add I2C ID table, report saturation
Date: Wed, 21 Oct 2026 11:00:56 +0300 [thread overview]
Message-ID: <athxOKkugAYL62F9@ashevche-desk.local> (raw)
In-Reply-To: <atdRJ3JqAyGWOnxf@mm-ntb-00805>
On Tue, Oct 20, 2026 at 01:31:51PM +0200, Jan Remes wrote:
> On Mon, 19 Oct 2026 11:50:10 +0300, Andy Shevchenko wrote:
> > On Mon, Oct 19, 2026 at 10:17:08AM +0200, Jan Remes wrote:
> > > On Sat, 17 Oct 2026 03:14:11 +0100, Jonathan Cameron wrote:
...
> > > FWIW, I don't think it to be very urgent, as people probably don't use
> > > it on x86-64 (seeing both as it had only DT probe support and that
> > > impacted users are likely to have noticed the oops).
> >
> > What do you mean by the second part of the sentence? It's as easy to use on
> > ACPI platforms as on DT, we have so nice trick called PRP0001, which allows to
> > enumerate "OF-only" drivers on ACPI platforms via SSDT overlays (or other means
> > of DSDT/SSDT provisioning).
> I did not know about the PRP0001 (thanks), so please disregard that
> argument. Still, I believe x86 users to be few if any, since the oops is
> quite easy to trigger
True.
> and AFAIK most x86 distro kernels ship without CONFIG_OF.
How is this relevant? This driver doesn't use any #ifdef CONFIG_OF or alike,
so most likely the driver is available for x86 as well.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-10-21 8:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 14:16 Jan Remes
2026-10-14 14:16 ` [PATCH v2 1/4] iio: light: tsl2591: don't divide by zero Jan Remes
2026-10-14 14:16 ` [PATCH v2 2/4] iio: light: tsl2591: add I2C device ID table Jan Remes
2026-10-14 14:16 ` [PATCH v2 3/4] iio: light: tsl2591: report saturation Jan Remes
2026-10-14 14:16 ` [PATCH v2 4/4] iio: light: tsl2591: improve lux calculation precision Jan Remes
2026-10-15 18:36 ` [PATCH v2 0/4] iio: light: tsl2591: fix lux calculation and precision, add I2C ID table, report saturation Andy Shevchenko
2026-10-17 2:14 ` Jonathan Cameron
2026-10-19 8:17 ` Jan Remes
2026-10-19 8:50 ` Andy Shevchenko
2026-10-20 11:31 ` Jan Remes
2026-10-21 8:00 ` Andy Shevchenko [this message]
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=athxOKkugAYL62F9@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jan.remes@mycroftmind.com \
--cc=jic23@kernel.org \
--cc=joe.g.sandom@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.triska@mycroftmind.com \
--cc=nuno.sa@analog.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
all inboxes | Powered by JetHome®