From: Bhanu Seshu Kumar Valluri <bhanuseshukumar@gmail.com>
To: Shrikant Raskar <raskar.shree97@gmail.com>,
jic23@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Cc: dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
matt@ranostay.sg, skhan@linuxfoundation.org,
david.hunter.linux@gmail.com, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH 1/2] dt-bindings: iio: max30100: Add pulse-width property
Date: Sat, 4 Oct 2025 08:52:08 +0530 [thread overview]
Message-ID: <21b1dc10-acad-43b9-a9c6-24abb2886856@gmail.com> (raw)
In-Reply-To: <20251004015623.7019-2-raskar.shree97@gmail.com>
On 04/10/25 07:26, Shrikant Raskar wrote:
> The MAX30100 sensor supports multiple LED pulse widths (200us, 400us,
> 800us, 1600us). These settings affect measurement resolution and power
> consumption. Until now, the driver always defaulted to 1600us.
>
> Introduce a new device tree property `maxim,pulse-width` that allows
> users to select the desired pulse width in microseconds from device
> tree.
>
> Valid values are: 200, 400, 800, 1600.
>
> This prepares for driver changes that read this property and configure
> the SPO2 register accordingly.
>
> Signed-off-by: Shrikant Raskar <raskar.shree97@gmail.com>
The subject prefix [PATCH 1/2] says it's a two part patch series. But I think
you send all changes in a single patch. If single patch use [PATCH] instead
of [PATCH 1/2].
next prev parent reply other threads:[~2025-10-04 3:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-04 1:56 [PATCH 0/2] iio: health: max30100: Add DT pulse-width support Shrikant Raskar
2025-10-04 1:56 ` [PATCH 1/2] dt-bindings: iio: max30100: Add pulse-width property Shrikant Raskar
2025-10-04 3:22 ` Bhanu Seshu Kumar Valluri [this message]
2025-10-04 6:19 ` Shrikant
2025-10-04 13:12 ` Jonathan Cameron
2025-10-06 3:04 ` Shrikant
2025-10-12 14:11 ` Jonathan Cameron
2025-10-12 16:52 ` Shrikant
2025-10-06 14:40 ` Krzysztof Kozlowski
2025-10-04 1:56 ` [PATCH 2/2] iio: health: max30100: Add pulse-width configuration via DT Shrikant Raskar
2025-10-04 13:16 ` Jonathan Cameron
2025-10-09 13:28 ` kernel test robot
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=21b1dc10-acad-43b9-a9c6-24abb2886856@gmail.com \
--to=bhanuseshukumar@gmail.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david.hunter.linux@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@ranostay.sg \
--cc=nuno.sa@analog.com \
--cc=raskar.shree97@gmail.com \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.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).