From: Jonathan Cameron <jic23@kernel.org>
To: Md Shofiqul Islam <shofiqtest@gmail.com>
Cc: linux-iio@vger.kernel.org, lars@metafoo.de, conor@kernel.org,
conor+dt@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/3] iio: health: add MAX86150 ECG and PPG biosensor driver
Date: Thu, 2 Jul 2026 02:41:04 +0100 [thread overview]
Message-ID: <20260702024104.206181f3@jic23-huawei> (raw)
In-Reply-To: <20260623201124.18271-1-shofiqtest@gmail.com>
On Tue, 23 Jun 2026 23:11:20 +0300
Md Shofiqul Islam <shofiqtest@gmail.com> wrote:
> Changes in v5 (addressing Conor Dooley and Sashiko review of v4):
No idea if someone else has commented on it in the nested threads
I'm seeing but never send a new patch version in reply to another.
It leads to really tricky to follow threads in a threading email
client + also ensures your whole series is pages up in the maintainers
backlog.
New version, new email thread.
Thanks,
Jonathan
>
> DT binding (Conor Dooley):
> - Rename binding file and compatible to adi,max86150 per ADI policy for
> former Maxim products.
> - Add missing power supply properties: avdd-supply (analog core),
> vref-supply (ECG reference); make all four supplies required.
> - Fix vdd-supply description: remove voltage tolerances; say "1.8 V".
> - Fix leds-supply description: say "typically 3.3 V" (datasheet max
> is 5.0 V, not 5.5 V as previously stated).
> - Rename example node to heart-rate@5e per prior DT art.
>
> Driver (Sashiko):
> - [High] Re-assign indio_dev->trig after trigger registration so the
> hardware trigger is the default and iio_trigger_validate_own_device
> accepts writes to current_trigger without a manual sysfs step.
> iio_device_unregister() releases the reference via iio_trigger_put().
> - [High] Switch from devm_request_irq() to devm_request_threaded_irq()
> with IRQF_ONESHOT. A hard handler returning IRQ_HANDLED on a
> level-triggered line unmasks the still-asserted INT pin and causes an
> immediate re-fire loop. IRQF_ONESHOT keeps the line masked until
> max86150_trigger_handler reads INT_STATUS1 and de-asserts the source.
> - [Medium] Fix overflow timestamps: when OVF_COUNTER > 0, pf->timestamp
> reflects an earlier A_FULL event and is no longer a valid anchor.
> Capture ktime_get_ns() at drain time and reconstruct timestamps
> relative to the newest surviving sample instead.
> - [Medium] Pad fifo_raw to ARCH_DMA_MINALIGN bytes so that buf starts
> in the next cacheline. Previously the 9-byte fifo_raw (DMA target)
> and buf (CPU push buffer) shared a cacheline, violating DMA API
> constraints flagged by CONFIG_DMA_API_DEBUG.
> - [Medium] Replace blind usleep_range() in read_raw() with
> regmap_read_poll_timeout() on the PPG_RDY bit. A fixed 11 ms sleep
> risks reading an empty FIFO if the internal oscillator starts slower
> than nominal; polling with a 25 ms timeout is robust.
>
> Link: https://lore.kernel.org/linux-iio/20260623174600.17100-1-shofiqtest@gmail.com/
> v4 cover letter
>
> Md Shofiqul Islam (3):
> dt-bindings: iio: health: add adi,max86150
> iio: health: add MAX86150 ECG and PPG biosensor driver
> MAINTAINERS: add entry for MAX86150 IIO health driver
>
> .../bindings/iio/health/adi,max86150.yaml | 78 ++
> MAINTAINERS | 7 +
> drivers/iio/health/Kconfig | 23 +
> drivers/iio/health/Makefile | 1 +
> drivers/iio/health/max86150.c | 730 ++++++++++++++++++
> 5 files changed, 839 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/health/adi,max86150.yaml
> create mode 100644 drivers/iio/health/max86150.c
>
next prev parent reply other threads:[~2026-07-02 1:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 14:01 [PATCH 0/1] iio: health: add MAX86150 ECG and PPG biosensor driver Md Shofiqul Islam
2026-06-23 14:01 ` [PATCH 1/1] " Md Shofiqul Islam
2026-06-23 14:38 ` Joshua Crofts
2026-06-23 15:38 ` Krzysztof Kozlowski
2026-06-30 16:52 ` Uwe Kleine-König
2026-06-23 15:55 ` [PATCH v2 0/3] " Md Shofiqul Islam
2026-06-23 15:55 ` [PATCH v2 1/3] dt-bindings: iio: health: add maxim,max86150 Md Shofiqul Islam
2026-06-23 15:55 ` [PATCH v2 2/3] iio: health: add MAX86150 ECG and PPG biosensor driver Md Shofiqul Islam
2026-06-23 15:55 ` [PATCH v2 3/3] MAINTAINERS: add entry for MAX86150 IIO health driver Md Shofiqul Islam
2026-06-23 17:45 ` [PATCH v4 0/3] iio: health: add MAX86150 ECG and PPG biosensor driver Md Shofiqul Islam
2026-06-23 17:45 ` [PATCH v4 1/3] dt-bindings: iio: health: add maxim,max86150 Md Shofiqul Islam
2026-06-23 17:45 ` [PATCH v4 2/3] iio: health: add MAX86150 ECG and PPG biosensor driver Md Shofiqul Islam
2026-06-23 20:52 ` Andy Shevchenko
2026-06-23 17:46 ` [PATCH v4 3/3] MAINTAINERS: add entry for MAX86150 IIO health driver Md Shofiqul Islam
2026-06-23 20:11 ` [PATCH v5 0/3] iio: health: add MAX86150 ECG and PPG biosensor driver Md Shofiqul Islam
2026-06-23 20:11 ` [PATCH v5 1/3] dt-bindings: iio: health: add adi,max86150 Md Shofiqul Islam
2026-06-25 6:33 ` Krzysztof Kozlowski
2026-07-02 2:58 ` Jonathan Cameron
2026-06-23 20:11 ` [PATCH v5 2/3] iio: health: add MAX86150 ECG and PPG biosensor driver Md Shofiqul Islam
2026-07-02 3:42 ` Jonathan Cameron
2026-06-23 20:11 ` [PATCH v5 3/3] MAINTAINERS: add entry for MAX86150 IIO health driver Md Shofiqul Islam
2026-06-24 6:22 ` Krzysztof Kozlowski
2026-06-24 6:53 ` Joshua Crofts
2026-07-02 1:41 ` Jonathan Cameron [this message]
2026-06-23 21:04 ` [PATCH v2 0/3] iio: health: add MAX86150 ECG and PPG biosensor driver David Lechner
2026-07-02 1:43 ` Jonathan Cameron
2026-06-23 16:43 ` [PATCH v3 " Md Shofiqul Islam
2026-06-23 16:43 ` [PATCH v3 1/3] dt-bindings: iio: health: add maxim,max86150 Md Shofiqul Islam
2026-06-23 17:53 ` Conor Dooley
2026-06-23 16:43 ` [PATCH v3 2/3] iio: health: add MAX86150 ECG and PPG biosensor driver Md Shofiqul Islam
2026-06-23 16:43 ` [PATCH v3 3/3] MAINTAINERS: add entry for MAX86150 IIO health driver Md Shofiqul Islam
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=20260702024104.206181f3@jic23-huawei \
--to=jic23@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--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 \
--cc=shofiqtest@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