From: Jonathan Cameron <jic23@kernel.org>
To: "Guido Günther" <agx@sigxcpu.org>
Cc: Tomas Novotny <tomas@novotny.cz>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
"Angus Ainslie (Purism)" <angus@akkea.ca>,
Marco Felsch <m.felsch@pengutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Nishant Malpani <nish.malpani25@gmail.com>
Subject: Re: [PATCH v4 2/5] dt-bindings: iio: Introduce common properties for iio sensors
Date: Sun, 12 Apr 2020 12:28:35 +0100 [thread overview]
Message-ID: <20200412122835.15f82420@archlinux> (raw)
In-Reply-To: <8b91f0b7fa76ca4b2f3cdc251411829f71f8d810.1586094535.git.agx@sigxcpu.org>
On Sun, 5 Apr 2020 15:50:29 +0200
Guido Günther <agx@sigxcpu.org> wrote:
> Introduce a file for common properties of iio sensors. So far this
> contains the new proximity-near-level property for proximity sensors
> that indicates when an object should be considered near.
>
> Signed-off-by: Guido Günther <agx@sigxcpu.org>
This works for me. However, I would like to give time for Rob and
others to comment on the syntax, naming etc of this file.
Thanks,
Jonathan
> ---
> .../devicetree/bindings/iio/common.yaml | 35 +++++++++++++++++++
> 1 file changed, 35 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/common.yaml
>
> diff --git a/Documentation/devicetree/bindings/iio/common.yaml b/Documentation/devicetree/bindings/iio/common.yaml
> new file mode 100644
> index 000000000000..97ffcb77043d
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/common.yaml
> @@ -0,0 +1,35 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/common.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Common properties for iio sensors
> +
> +maintainers:
> + - Jonathan Cameron <jic23@kernel.org>
> + - Guido Günther <agx@sigxcpu.org>
> +
> +description: |
> + This document defines device tree properties common to several iio
> + sensors. It doesn't constitue a device tree binding specification by itself but
> + is meant to be referenced by device tree bindings.
> +
> + When referenced from sensor tree bindings the properties defined in this
> + document are defined as follows. The sensor tree bindings are responsible for
> + defining whether each property is required or optional.
> +
> +properties:
> + proximity-near-level:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: |
> + For proximity sensors whether an object can be considered near to the
> + device depends on parameters like sensor position, covering glass and
> + aperture. This value gives an indication to userspace for which
> + sensor readings this is the case.
> +
> + Raw proximity values equal or above this level should be
> + considered 'near' to the device (an object is near to the
> + sensor).
> +
> +...
next prev parent reply other threads:[~2020-04-12 11:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 13:50 [PATCH v4 0/5] iio: vcnl4000: Export near level property for proximity sensor Guido Günther
2020-04-05 13:50 ` [PATCH v4 1/5] dt-bindings: iio: vcnl4000: convert bindings to YAML format Guido Günther
2020-04-05 13:50 ` [PATCH v4 2/5] dt-bindings: iio: Introduce common properties for iio sensors Guido Günther
2020-04-12 11:28 ` Jonathan Cameron [this message]
2020-04-14 21:49 ` Rob Herring
2020-04-18 18:03 ` Jonathan Cameron
2020-04-05 13:50 ` [PATCH v4 3/5] dt-bindings: iio: light: vcnl4000: Add proximity-near-level Guido Günther
2020-04-14 21:50 ` Rob Herring
2020-04-18 18:04 ` Jonathan Cameron
2020-04-05 13:50 ` [PATCH v4 4/5] iio: vcnl4000: Export near level property for proximity sensor Guido Günther
2020-04-18 18:05 ` Jonathan Cameron
2020-04-05 13:50 ` [PATCH v4 5/5] Documentation: ABI: document IIO in_proximity_nearlevel file Guido Günther
2020-04-18 18:06 ` 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=20200412122835.15f82420@archlinux \
--to=jic23@kernel.org \
--cc=agx@sigxcpu.org \
--cc=andy.shevchenko@gmail.com \
--cc=angus@akkea.ca \
--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.felsch@pengutronix.de \
--cc=nish.malpani25@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=tglx@linutronix.de \
--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 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.