[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <21b1dc10-acad-43b9-a9c6-24abb2886856@gmail.com>
Date: Sat, 4 Oct 2025 08:52:08 +0530
From: Bhanu Seshu Kumar Valluri <bhanuseshukumar@...il.com>
To: Shrikant Raskar <raskar.shree97@...il.com>, jic23@...nel.org,
robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org
Cc: dlechner@...libre.com, nuno.sa@...log.com, andy@...nel.org,
matt@...ostay.sg, skhan@...uxfoundation.org, david.hunter.linux@...il.com,
linux-iio@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-kernel-mentees@...ts.linux.dev
Subject: Re: [PATCH 1/2] dt-bindings: iio: max30100: Add pulse-width property
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@...il.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].
Powered by blists - more mailing lists