From: Jonathan Cameron <jic23@kernel.org>
To: Emil Gedenryd <emil.gedenryd@axis.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>,
Andreas Dannenberg <dannenberg@ti.com>,
<linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>, <kernel@axis.com>
Subject: Re: [PATCH v4 2/2] iio: light: opt3001: add support for TI's opt3002 light sensor
Date: Sun, 6 Oct 2024 14:16:24 +0100 [thread overview]
Message-ID: <20241006141624.3fa5bf34@jic23-huawei> (raw)
In-Reply-To: <20241003-add_opt3002-v4-2-c550dc4591b4@axis.com>
On Thu, 3 Oct 2024 14:22:17 +0200
Emil Gedenryd <emil.gedenryd@axis.com> wrote:
> TI's opt3002 light sensor shares most properties with the opt3001
> model, with the exception of supporting a wider spectrum range.
>
> Add support for TI's opt3002 by extending the TI opt3001 driver.
>
> Datasheet: https://www.ti.com/product/OPT3002
> Signed-off-by: Emil Gedenryd <emil.gedenryd@axis.com>
> ---
> drivers/iio/light/Kconfig | 2 +-
> drivers/iio/light/opt3001.c | 189 ++++++++++++++++++++++++++++++++++++--------
> 2 files changed, 157 insertions(+), 34 deletions(-)
>
> diff --git a/drivers/iio/light/Kconfig b/drivers/iio/light/Kconfig
> index b68dcc1fbaca..c35bf962dae6 100644
> --- a/drivers/iio/light/Kconfig
> +++ b/drivers/iio/light/Kconfig
> @@ -461,7 +461,7 @@ config OPT3001
> depends on I2C
> help
> If you say Y or M here, you get support for Texas Instruments
> - OPT3001 Ambient Light Sensor.
> + OPT3001 Ambient Light Sensor, OPT3002 Light-to-Digital Sensor.
>
> If built as a dynamically linked module, it will be called
> opt3001.
> diff --git a/drivers/iio/light/opt3001.c b/drivers/iio/light/opt3001.c
> index 176e54bb48c3..ff7fc0d4b08f 100644
> --- a/drivers/iio/light/opt3001.c
> +++ b/drivers/iio/light/opt3001.c
> @@ -70,6 +70,35 @@
> #define OPT3001_RESULT_READY_SHORT 150
> #define OPT3001_RESULT_READY_LONG 1000
>
> +struct opt3001_scale {
> + int val;
> + int val2;
> +};
> +
> +struct opt3001_chip_info {
> + const struct iio_chan_spec (*channels)[2];
> + enum iio_chan_type chan_type;
> + int num_channels;
> +
> + const struct opt3001_scale (*scales)[12];
This doesn't compile for me as one of the two options only
has 11 entries. You could either force them to be 12
entries each or use a pointer without the size and
add a num_scales entry in here.
Jonathan
next prev parent reply other threads:[~2024-10-06 13:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 12:22 [PATCH v4 0/2] iio: light: opt3001: add support for TI's opt3002 light sensor Emil Gedenryd
2024-10-03 12:22 ` [PATCH v4 1/2] dt-bindings: iio: light: opt3001: add compatible for opt3002 Emil Gedenryd
2024-10-03 12:22 ` [PATCH v4 2/2] iio: light: opt3001: add support for TI's opt3002 light sensor Emil Gedenryd
2024-10-06 13:16 ` Jonathan Cameron [this message]
2024-10-07 7:19 ` Emil Gedenryd
2024-10-10 17:47 ` Jonathan Cameron
2024-10-11 7:12 ` Emil Gedenryd
2024-10-12 15:10 ` Jonathan Cameron
2024-10-14 6:18 ` Emil Gedenryd
2024-10-21 18:28 ` Jonathan Cameron
2024-10-22 7:16 ` Emil Gedenryd
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=20241006141624.3fa5bf34@jic23-huawei \
--to=jic23@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dannenberg@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=emil.gedenryd@axis.com \
--cc=kernel@axis.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).