devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emil Gedenryd <emil.gedenryd@axis.com>
To: Jonathan Cameron <jic23@kernel.org>,
	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>
Cc: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<devicetree@vger.kernel.org>,
	Emil Gedenryd <emil.gedenryd@axis.com>, <kernel@axis.com>,
	Conor Dooley <conor.dooley@microchip.com>
Subject: [PATCH v4 0/2] iio: light: opt3001: add support for TI's opt3002 light sensor
Date: Thu, 3 Oct 2024 14:22:15 +0200	[thread overview]
Message-ID: <20241003-add_opt3002-v4-0-c550dc4591b4@axis.com> (raw)

TI's opt3002 light-to-digital sensor provides the functionality
of an optical power meter within a single device. It shares a lot of
similarities with their opt3001 model but has a wide spectral bandwidth,
ranging from 300 nm to 1000 nm.

This patch set adds support for the TI opt3002 by extending the opt3001
driver. In addition, a missing full-scale range value for the opt3001 is
added, resulting in higher precision when setting event trigger values.

Datasheet: http://www.ti.com/product/OPT3002

Signed-off-by: Emil Gedenryd <emil.gedenryd@axis.com>
---
Changes in v4:
- Drop applied patch: "iio: light: opt3001: add missing full-scale range value"
- Add num_channels field to opt3001_chip_info
- Use i2c_get_match_data() instead of device_get_match_data()
- Link to v3: https://lore.kernel.org/r/20240916-add_opt3002-v3-0-984b190cd68c@axis.com

Changes in v3:
- Include difference between opt3001 and opt3002 in commit message for
  dt-binding patch.
- Remove whitespace between tags in commit message for opt3002 patch.
- Rename opt300x_chip_info to opt3001_chip_info.
- Add documentation for mathematical constants in opt3001_chip_info.
- Only check return value after opt3001_read_id if chip has id register
  in opt3001_probe.
- Change opt3002 channel mask to IIO_CHAN_INFO_RAW.
- Link to v2: https://lore.kernel.org/r/20240913-add_opt3002-v2-0-69e04f840360@axis.com

Changes in v2:
- Move dt-binding patch to before implementation.
- Fix dt-binding compatible definition.
- Clarify bug description for missing full-scale range value.
- Remove model enum from chip info and all in-function switch-case
  statements.
- Move model-specific channels and mathematic constants to chip info.
- Add valid match data to opt3001_id array
- Skip call to function opt3001_read_id() if model doesn't have a device
  id register.
- Link to v1: https://lore.kernel.org/r/20240905-add_opt3002-v1-0-a5ae21b924fb@axis.com

---
Emil Gedenryd (2):
      dt-bindings: iio: light: opt3001: add compatible for opt3002
      iio: light: opt3001: add support for TI's opt3002 light sensor

 .../devicetree/bindings/iio/light/ti,opt3001.yaml  |   4 +-
 drivers/iio/light/Kconfig                          |   2 +-
 drivers/iio/light/opt3001.c                        | 189 +++++++++++++++++----
 3 files changed, 160 insertions(+), 35 deletions(-)
---
base-commit: e2df62bb0fadc8ae16aa3bb88ee05ee7e037046b
change-id: 20240828-add_opt3002-40552c1a2f77

Best regards,
-- 
Emil Gedenryd <emil.gedenryd@axis.com>


             reply	other threads:[~2024-10-03 12:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-03 12:22 Emil Gedenryd [this message]
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
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=20241003-add_opt3002-v4-0-c550dc4591b4@axis.com \
    --to=emil.gedenryd@axis.com \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=dannenberg@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --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).