From: Waqar Hameed <waqar.hameed@axis.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>, <kernel@axis.com>,
<linux-kernel@vger.kernel.org>, <linux-iio@vger.kernel.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 0/3] Add driver for Nicera D3-323-AA PIR sensor
Date: Fri, 16 May 2025 19:14:45 +0200 [thread overview]
Message-ID: <pndy0uwiika.fsf@axis.com> (raw)
In-Reply-To: <d746c1b4-4794-498d-9a6c-a1ac1c58357c@kernel.org> (Krzysztof Kozlowski's message of "Fri, 9 May 2025 17:09:17 +0200")
On Fri, May 09, 2025 at 17:09 +0200 Krzysztof Kozlowski <krzk@kernel.org> wrote:
> On 09/05/2025 17:03, Waqar Hameed wrote:
>> Nicera D3-323-AA is a PIR sensor for human detection. It has support for
>> raw data measurements and detection notification. The communication
>> protocol is custom made and therefore needs to be GPIO bit banged.
>>
>> Previously, there has been an attempt to add a driver for this device
>> [1]. However, that driver was written for the wrong sub-system. `hwmon`
>
> So that's a v2. Mark your patches correctly.
I figured that since it was a complete rewrite (and from another
author), I'd start a new series. But I also understand your point.
To not confuse others, I'll mark the next one as V2 instead (if that's
fine with you).
>
>> is clearly not a suitable framework for a proximity device.
>>
>> In this series, we add a driver for support for event notification for
>> detections through IIO (the more appropriate sub-system!). The various
>> settings have been mapped to existing `sysfs` ABIs in the IIO framework.
>>
>> The public datasheet [2] is quite sparse. A more detailed version can be
>> obtained through the company.
>>
>> [1] https://lore.kernel.org/lkml/20241212042412.702044-2-Hermes.Zhang@axis.com/
> Read the comments given in that review:
> https://lore.kernel.org/lkml/wy7nyg3cztixe5y5rg4kbsbbly32h547hwumwwvrfme4fdgsj5@znfpypleebrb/
>
> You repeated same mistakes, which means I did same review second time
> which is waste of my time.
I'm really sorry! I actually completely missed your response there.
Thank you again for reviewing! I know it's a lot of work sometimes...
next prev parent reply other threads:[~2025-05-16 17:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 15:03 [PATCH 0/3] Add driver for Nicera D3-323-AA PIR sensor Waqar Hameed
2025-05-09 15:03 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add Nicera Waqar Hameed
2025-05-09 15:03 ` [PATCH 3/3] iio: Add driver for Nicera D3-323-AA PIR sensor Waqar Hameed
2025-05-11 7:57 ` Christophe JAILLET
2025-05-16 17:16 ` Waqar Hameed
2025-05-11 12:14 ` Jonathan Cameron
2025-05-16 17:16 ` Waqar Hameed
2025-05-18 17:38 ` Jonathan Cameron
2025-05-20 11:27 ` Waqar Hameed
2025-05-25 9:30 ` Jonathan Cameron
2025-05-27 14:48 ` Waqar Hameed
2025-05-31 15:10 ` Jonathan Cameron
2025-06-02 15:09 ` Waqar Hameed
2025-06-14 22:05 ` Waqar Hameed
2025-05-09 15:03 ` [PATCH 2/3] dt-bindings: iio: proximity: Add " Waqar Hameed
2025-05-09 15:06 ` Krzysztof Kozlowski
2025-05-16 17:15 ` Waqar Hameed
2025-05-20 6:36 ` Krzysztof Kozlowski
2025-05-20 12:00 ` Waqar Hameed
2025-05-09 15:09 ` [PATCH 0/3] Add driver for " Krzysztof Kozlowski
2025-05-16 17:14 ` Waqar Hameed [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-14 21:56 Waqar Hameed
2025-06-14 22:09 ` Waqar Hameed
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=pndy0uwiika.fsf@axis.com \
--to=waqar.hameed@axis.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=kernel@axis.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.