From: Jonathan Cameron <jic23@kernel.org>
To: "Angus Ainslie (Purism)" <angus@akkea.ca>
Cc: angus.ainslie@puri.sm, Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Tomas Novotny <tomas@novotny.cz>,
Brian Masney <masneyb@onstation.org>,
Robert Eshleman <bobbyeshleman@gmail.com>,
Mathieu Othacehe <m.othacehe@gmail.com>,
Parthiban Nallathambi <pn@denx.de>, ryang <decatf@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: iio: light: Document the VCNL4xx0 device tree bindings
Date: Sat, 16 Mar 2019 17:15:17 +0000 [thread overview]
Message-ID: <20190316171517.4c783134@archlinux> (raw)
In-Reply-To: <20190315215425.24140-3-angus@akkea.ca>
On Fri, 15 Mar 2019 14:54:25 -0700
"Angus Ainslie (Purism)" <angus@akkea.ca> wrote:
> devicetree hooks where added to the VCNL4xx0 light and proximity
> sensor driver.
>
> Signed-off-by: Angus Ainslie (Purism) <angus@akkea.ca>
Please avoid wild cards in naming. It goes wrong too often. People can grep
if they want to see if their device is supported by any drivers rather
than try to figure out wildcards.
> ---
> .../devicetree/bindings/iio/light/vcnl4xx0.txt | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/light/vcnl4xx0.txt
>
> diff --git a/Documentation/devicetree/bindings/iio/light/vcnl4xx0.txt b/Documentation/devicetree/bindings/iio/light/vcnl4xx0.txt
> new file mode 100644
> index 000000000000..d61cf3c121c3
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/light/vcnl4xx0.txt
> @@ -0,0 +1,15 @@
> +VISHAY VCNL4xx0 - Ambient Light and proximity sensor
> +
> +This driver supports the VCNL4000/10/20/40 and VCNL4200
> +
> +Required properties:
> +
> + -compatible: should be "vishay,vcnl4000" or "vishay,vcnl4040"
One per line.
I'd also like to see all the options in the list. We already seem
to have an undocumented difference between your new part and some
of the older ones. It's always better for people to use the 'most
correct' part name the can.
> + -reg: I2C address of the sensor, should be 0x60
> +
> +Example:
> +
> +light-sensor@60 {
> + compatible = "vishay,vcnl4040";
> + reg = <0x60>;
> +};
prev parent reply other threads:[~2019-03-16 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 21:54 [PATCH 0/2] Add a VCNL4040 light and proximity driver Angus Ainslie (Purism)
2019-03-15 21:54 ` [PATCH 1/2] iio: light: vcnl4000 add support for the VCNL4040 proximity and light sensor Angus Ainslie (Purism)
2019-03-16 17:13 ` Jonathan Cameron
2019-03-15 21:54 ` [PATCH 2/2] dt-bindings: iio: light: Document the VCNL4xx0 device tree bindings Angus Ainslie (Purism)
2019-03-16 17:15 ` Jonathan Cameron [this message]
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=20190316171517.4c783134@archlinux \
--to=jic23@kernel.org \
--cc=angus.ainslie@puri.sm \
--cc=angus@akkea.ca \
--cc=bobbyeshleman@gmail.com \
--cc=decatf@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.othacehe@gmail.com \
--cc=mark.rutland@arm.com \
--cc=masneyb@onstation.org \
--cc=pmeerw@pmeerw.net \
--cc=pn@denx.de \
--cc=robh+dt@kernel.org \
--cc=tomas@novotny.cz \
/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;
as well as URLs for NNTP newsgroup(s).