From: Jonathan Cameron <jic23@kernel.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>,
Matti Vaittinen <mazziesaccount@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Emil Gedenryd <emil.gedenryd@axis.com>,
Arthur Becker <arthur.becker@sentec.com>,
Mudit Sharma <muditsharma.info@gmail.com>,
Per-Daniel Olsson <perdaniel.olsson@axis.com>,
Subhajit Ghosh <subhajit.ghosh@tweaklogic.com>,
Ivan Orlov <ivan.orlov0322@gmail.com>,
David Heidelberg <david@ixit.cz>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2 2/3] iio: light: Add support for AL3000a illuminance sensor
Date: Mon, 17 Feb 2025 14:24:33 +0000 [thread overview]
Message-ID: <20250217142433.12183a17@jic23-huawei> (raw)
In-Reply-To: <CAPVz0n1529ydFRHn9N3jEsS8Rhdf-c4xECkMd9TDczzBTNuJzA@mail.gmail.com>
Hi,
> > > +static int al3000a_read_raw(struct iio_dev *indio_dev,
> > > + struct iio_chan_spec const *chan, int *val,
> > > + int *val2, long mask)
> > > +{
> > > + struct al3000a_data *data = iio_priv(indio_dev);
> > > + int ret, gain;
> > > +
> > > + switch (mask) {
> > > + case IIO_CHAN_INFO_RAW:
> > > + ret = regmap_read(data->regmap, AL3000A_REG_DATA, &gain);
> > > + if (ret < 0)
> > > + return ret;
> > > +
> > > + *val = lux_table[gain & AL3000A_GAIN_MASK];
> >
> > I may have misinterpreted the other thread. IS this value in lux?
> > If it is make this channel IIO_CHAN_INFO_PROCESSED instead.
> >
>
> This is actually a really good hint, I will check if this works out
> and if yes, then definitely will use it. Thank you.
From your other reply it seems we have no idea of the correct scaling.
If that is the case, then channel type should be IIO_INTENSITY as
I assume we also have no idea if the light sensitivity curve is
matched to that required for illuminance (which approximates the
sensitivity of the human eye). Various datasheets provide completely
garbage conversion formulas btw so even if we have data this can
be problematic. One recent sensor was using a green filter and
saying illuminance in lux was 1.2 * green which was assuming their
own definition of white light.
Jonathan
next prev parent reply other threads:[~2025-02-17 14:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 10:31 [PATCH v2 0/3] iio: light: add al3000a als support Svyatoslav Ryhel
2025-02-15 10:31 ` [PATCH v2 1/3] dt-bindings: iio: light: al3010: add al3000a support Svyatoslav Ryhel
2025-02-16 14:42 ` Jonathan Cameron
2025-02-16 14:44 ` Svyatoslav Ryhel
2025-02-17 14:18 ` Jonathan Cameron
2025-02-15 10:31 ` [PATCH v2 2/3] iio: light: Add support for AL3000a illuminance sensor Svyatoslav Ryhel
2025-02-15 14:12 ` David Heidelberg
2025-02-15 14:22 ` Svyatoslav Ryhel
2025-02-16 14:44 ` Jonathan Cameron
2025-02-16 14:47 ` Svyatoslav Ryhel
2025-02-17 14:20 ` Jonathan Cameron
2025-02-16 14:54 ` Jonathan Cameron
2025-02-16 15:00 ` Svyatoslav Ryhel
2025-02-17 14:24 ` Jonathan Cameron [this message]
2025-02-17 14:32 ` Svyatoslav Ryhel
2025-02-22 12:05 ` Jonathan Cameron
2025-02-22 12:11 ` Svyatoslav Ryhel
2025-02-15 10:31 ` [PATCH v2 3/3] ARM: tegra: tf101: Add al3000a illuminance sensor node Svyatoslav Ryhel
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=20250217142433.12183a17@jic23-huawei \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arthur.becker@sentec.com \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=emil.gedenryd@axis.com \
--cc=ivan.orlov0322@gmail.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=muditsharma.info@gmail.com \
--cc=perdaniel.olsson@axis.com \
--cc=robh@kernel.org \
--cc=subhajit.ghosh@tweaklogic.com \
--cc=thierry.reding@gmail.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