From: Jonathan Cameron <jic23@kernel.org>
To: Andreas Klinger <ak@it-klinger.de>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, mripard@kernel.org,
shawnguo@kernel.org, heiko@sntech.de, icenowy@aosc.io,
laurent.pinchart@ideasonboard.com, knaack.h@gmx.de,
lars@metafoo.de, pmeerw@pmeerw.net, gregkh@linuxfoundation.org,
christophe.jaillet@wanadoo.fr, tglx@linutronix.de,
mchehab+samsung@kernel.org, davem@davemloft.net,
paulmck@linux.ibm.com, devicetree@vger.kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] dt-bindings: add parallax ping sensors
Date: Sun, 10 Nov 2019 16:59:38 +0000 [thread overview]
Message-ID: <20191110165938.2f680803@archlinux> (raw)
In-Reply-To: <20191107130027.k2uo547xrfiuxgb7@arbad>
On Thu, 7 Nov 2019 14:00:29 +0100
Andreas Klinger <ak@it-klinger.de> wrote:
> Add dt-bindings for parallax PING))) and LaserPING iio sensors, which
> are used for measuring distances.
>
> Signed-off-by: Andreas Klinger <ak@it-klinger.de>
> ---
> .../bindings/iio/proximity/parallax-ping.yaml | 51 ++++++++++++++++++++++
> 1 file changed, 51 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/proximity/parallax-ping.yaml
>
> diff --git a/Documentation/devicetree/bindings/iio/proximity/parallax-ping.yaml b/Documentation/devicetree/bindings/iio/proximity/parallax-ping.yaml
> new file mode 100644
> index 000000000000..ab8dbdf4f04a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/proximity/parallax-ping.yaml
> @@ -0,0 +1,51 @@
> +# SPDX-License-Identifier: GPL-2.0-or-later
Rob has been asking people if they mind adding a BSD-2-CLAUSE as an
and additional license on new bindings they have the copyright on.
Otherwise seems fine to me.
Thanks,
Jonathan
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/proximity/parallax-ping.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Parallax PING))) and LaserPING range finder
> +
> +maintainers:
> + - Andreas Klinger <ak@it-klinger.de>
> +
> +description: |
> + Bit-banging driver using one GPIO:
> + - ping-gpio is raised by the driver to start measurement
> + - direction of ping-gpio is then switched into input with an interrupt
> + for receiving distance value as PWM signal
> +
> + Specifications about the devices can be found at:
> + http://parallax.com/sites/default/files/downloads/28041-LaserPING-2m-Rangefinder-Guide.pdf
> + http://parallax.com/sites/default/files/downloads/28015-PING-Documentation-v1.6.pdf
> +
> +properties:
> + compatible:
> + enum:
> + - parallax,ping
> + - parallax,laserping
> +
> + ping-gpios:
> + description:
> + Definition of the GPIO for the triggering and echo (output and input)
> + This GPIO is set for about 5 us by the driver to tell the device it
> + should initiate the measurement cycle. Afterwards the GPIO is switched
> + to input direction with an interrupt. The device sets it and the
> + length of the input signal corresponds to the measured distance.
> + It needs to be an GPIO which is able to deliver an interrupt because
> + the time between two interrupts is measured in the driver.
> + See Documentation/devicetree/bindings/gpio/gpio.txt for information
> + on how to specify a consumer gpio.
> + maxItems: 1
> +
> +required:
> + - compatible
> + - ping-gpios
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> + proximity {
> + compatible = "parallax,laserping";
> + ping-gpios = <&gpio0 26 GPIO_ACTIVE_HIGH>;
> + };
next prev parent reply other threads:[~2019-11-10 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 13:00 [PATCH 2/5] dt-bindings: add parallax ping sensors Andreas Klinger
2019-11-10 16:59 ` Jonathan Cameron [this message]
2019-11-13 14:16 ` Rob Herring
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=20191110165938.2f680803@archlinux \
--to=jic23@kernel.org \
--cc=ak@it-klinger.de \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=icenowy@aosc.io \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=mripard@kernel.org \
--cc=paulmck@linux.ibm.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=tglx@linutronix.de \
/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).