From: Waqar Hameed <waqar.hameed@axis.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, <linux-iio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel@axis.com>
Subject: Re: [PATCH 1/2] dt-bindings: iio: proximity: Add bindings for Murata IRS-D200
Date: Mon, 19 Jun 2023 12:40:39 +0200 [thread overview]
Message-ID: <pnd1qi73dbu.fsf@axis.com> (raw)
In-Reply-To: <07a6766e-7e2b-22fa-6f20-3a8ab7019635@linaro.org>
On Sat, Jun 17, 2023 at 10:55 +0200 Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
> On 16/06/2023 17:10, Waqar Hameed wrote:
>> Murata IRS-D200 is a PIR sensor for human detection. It uses the I2C bus
>> for communication with interrupt support. Add devicetree bindings
>> requiring the compatible string, I2C slave address (reg) and interrupts.
>
> Thank you for your patch. There is something to discuss/improve. I have
> actually only remark about DTS example, but since I expect resend two
> more nits as well.
>
>
> A nit, subject: drop second/last, redundant "bindings for". The
> "dt-bindings" prefix is already stating that these are bindings.
Alright, will change to "dt-bindings: iio: proximity: Add Murata
IRS-D200".
[...]
>> +maintainers:
>> + - Waqar Hameed <waqar.hameed@axis.com>
>> +
>> +description: |
>
> Nit, do not need '|' unless you need to preserve formatting.
Yes, will remove (a remnant from previous version that had multiple
lines... Sorry!).
[...]
>> +examples:
>> + - |
>> + #include <dt-bindings/interrupt-controller/irq.h>
>> +
>> + i2c {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + pir@48 {
>
> Node names should be generic. See also explanation and list of examples
> in DT specification:
> https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
>
> so I guess: proximity@?
On that list there is "temperature-sensor". Would it make sense then to
call it "proximity-sensor"?
next prev parent reply other threads:[~2023-06-19 11:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 15:10 [PATCH 0/2] Add driver for Murata IRS-D200 Waqar Hameed
2023-06-16 15:10 ` [PATCH 1/2] dt-bindings: iio: proximity: Add bindings " Waqar Hameed
2023-06-17 8:55 ` Krzysztof Kozlowski
2023-06-19 10:40 ` Waqar Hameed [this message]
2023-06-19 11:29 ` Krzysztof Kozlowski
2023-06-17 12:55 ` Jonathan Cameron
2023-06-19 10:41 ` Waqar Hameed
2023-07-02 10:34 ` Jonathan Cameron
2023-06-16 15:10 ` [PATCH 2/2] iio: Add driver " Waqar Hameed
2023-06-17 1:37 ` Lars-Peter Clausen
2023-06-19 11:21 ` Waqar Hameed
2023-06-17 13:35 ` Jonathan Cameron
2023-06-19 11:24 ` Waqar Hameed
2023-06-25 11:06 ` Jonathan Cameron
2023-06-30 8:54 ` Waqar Hameed
2023-07-02 10:42 ` Jonathan Cameron
2023-07-03 8:59 ` Waqar Hameed
2023-07-05 7:50 ` Jonathan Cameron
2023-07-12 15:33 ` Waqar Hameed
2023-07-15 16:51 ` Jonathan Cameron
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=pnd1qi73dbu.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=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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.