linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Alexandre Mergnat <amergnat@baylibre.com>
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
	linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
	baylibre-upstreaming@groups.io, dmitry.torokhov@gmail.com,
	linux-input@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/3] dt-bindings: iio: position: Add docs pat9125
Date: Sun, 14 Jul 2019 11:57:50 +0100	[thread overview]
Message-ID: <20190714115750.454f5ef0@archlinux> (raw)
In-Reply-To: <20190713080455.17513-3-amergnat@baylibre.com>

On Sat, 13 Jul 2019 10:04:54 +0200
Alexandre Mergnat <amergnat@baylibre.com> wrote:

> Add documentation for the optical tracker PAT9125 and
> "position" directory for chip which can provides position data.
> 
> Signed-off-by: Alexandre Mergnat <amergnat@baylibre.com>
Whilst this one predates my statement that I wanted all bindings
in YAML going forwards, it will want converting at some stage
and if you have time now it would be great to do so!

Thanks,

Jonathan

> ---
>  .../bindings/iio/position/pat9125.txt          | 18 ++++++++++++++++++
>  1 file changed, 18 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/iio/position/pat9125.txt
> 
> diff --git a/Documentation/devicetree/bindings/iio/position/pat9125.txt b/Documentation/devicetree/bindings/iio/position/pat9125.txt
> new file mode 100644
> index 000000000000..4028aeef9b42
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/position/pat9125.txt
> @@ -0,0 +1,18 @@
> +PixArt Imaging PAT9125 Optical Tracking Miniature Chip device driver
> +
> +Required properties:
> +	- compatible: must be "pixart,pat9125"
> +	- reg: i2c address where to find the device
> +	- interrupts: the sole interrupt generated by the device
> +
> +	Refer to interrupt-controller/interrupts.txt for generic
> +	interrupt client node bindings.
> +
> +Example:
> +
> +pat9125@75 {
> +	compatible = "pixart,pat9125";
> +	reg = <0x75>;
> +	interrupt-parent = <&gpio3>;
> +	interrupts = <12 IRQ_TYPE_EDGE_FALLING>;
> +};


  reply	other threads:[~2019-07-14 10:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-13  8:04 [PATCH v4 0/3] Add PAT9125 optical tracker driver Alexandre Mergnat
2019-07-13  8:04 ` [PATCH v4 1/3] dt-bindings: Add pixart vendor Alexandre Mergnat
2019-08-12 22:46   ` Rob Herring
2019-07-13  8:04 ` [PATCH v4 2/3] dt-bindings: iio: position: Add docs pat9125 Alexandre Mergnat
2019-07-14 10:57   ` Jonathan Cameron [this message]
2019-07-13  8:04 ` [PATCH v4 3/3] iio: Add PAT9125 optical tracker sensor Alexandre Mergnat
2019-07-14 10:56   ` Jonathan Cameron
2019-07-14 13:09   ` Peter Meerwald-Stadler
  -- strict thread matches above, loose matches on Subject: below --
2019-07-12  9:40 [PATCH v4 0/3] Add PAT9125 optical tracker driver Alexandre Mergnat
2019-07-12  9:40 ` [PATCH v4 2/3] dt-bindings: iio: position: Add docs pat9125 Alexandre Mergnat

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=20190714115750.454f5ef0@archlinux \
    --to=jic23@kernel.org \
    --cc=amergnat@baylibre.com \
    --cc=baylibre-upstreaming@groups.io \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --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 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).