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>,
Conor Dooley <conor+dt@kernel.org>, <kernel@axis.com>,
<linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] dt-bindings: iio: proximity: Add Nicera D3-323-AA PIR sensor
Date: Wed, 18 Jun 2025 12:37:11 +0200 [thread overview]
Message-ID: <pndjz59l4iw.fsf@axis.com> (raw)
In-Reply-To: <20250617-vagabond-fulmar-of-penetration-dbe048@kuoka> (Krzysztof Kozlowski's message of "Tue, 17 Jun 2025 11:06:08 +0200")
On Tue, Jun 17, 2025 at 11:06 +0200 Krzysztof Kozlowski <krzk@kernel.org> wrote:
> On Sun, Jun 15, 2025 at 12:14:02AM GMT, Waqar Hameed wrote:
>> +examples:
>> + - |
>> + proximity {
>> + compatible = "nicera,d3323aa";
>> + vdd-supply = <®ulator_3v3>;
>> + vout-clk-gpios = <&gpio 78 0>;
>> + data-gpios = <&gpio 76 0>;
>
> Same comment as before.
I removed the include header thinking that would be fine, since there
were already a bunch of other examples just using `0` as the GPIO flag
(without the include). I'll re-add the include header in next version
then and use `GPIO_ACTIVE_HIGH` on both `-gpios`.
next prev parent reply other threads:[~2025-06-18 10:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 22:13 [PATCH v2 0/3] Add driver for Nicera D3-323-AA PIR sensor Waqar Hameed
2025-06-14 22:14 ` [PATCH v2 2/3] dt-bindings: iio: proximity: Add " Waqar Hameed
2025-06-17 9:06 ` Krzysztof Kozlowski
2025-06-18 10:37 ` Waqar Hameed [this message]
2025-06-14 22:14 ` [PATCH v2 3/3] iio: Add driver for " Waqar Hameed
2025-06-22 11:07 ` Jonathan Cameron
2025-06-24 19:35 ` Waqar Hameed
2025-06-28 17:11 ` Jonathan Cameron
2025-06-30 21:57 ` Waqar Hameed
2025-06-22 10:33 ` [PATCH v2 0/3] " Jonathan Cameron
2025-06-24 19:36 ` 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=pndjz59l4iw.fsf@axis.com \
--to=waqar.hameed@axis.com \
--cc=conor+dt@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox