linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Jeff LaBundy <jeff@labundy.com>
Cc: dmitry.torokhov@gmail.com, thierry.reding@gmail.com,
	jic23@kernel.org, devicetree@vger.kernel.org,
	linux-input@vger.kernel.org, u.kleine-koenig@pengutronix.de,
	linux-pwm@vger.kernel.org, knaack.h@gmx.de, lars@metafoo.de,
	pmeerw@pmeerw.net, linux-iio@vger.kernel.org, robh+dt@kernel.org,
	mark.rutland@arm.com
Subject: Re: [PATCH v5 1/7] dt-bindings: Add bindings for Azoteq IQS620A/621/622/624/625
Date: Mon, 24 Feb 2020 11:14:22 +0000	[thread overview]
Message-ID: <20200224111422.GR3494@dell> (raw)
In-Reply-To: <1581895931-6056-2-git-send-email-jeff@labundy.com>

On Sun, 16 Feb 2020, Jeff LaBundy wrote:

> This patch adds device tree bindings for the Azoteq IQS620A, IQS621,
> IQS622, IQS624 and IQS625 multi-function sensors.
> 
> A total of three bindings are presented (one MFD and two child nodes);
> they are submitted as a single patch because the child node bindings
> have no meaning in the absence of the MFD binding.
> 
> Signed-off-by: Jeff LaBundy <jeff@labundy.com>
> Reviewed-by: Rob Herring <robh@kernel.org>
> ---
> Changes in v5:
>   - Corrected spelling of "data sheets" to "datasheets"
>   - Replaced words "additional air button" with "proximity-activated function"
>     in comment above first example
> 
> Changes in v4:
>   - None
> 
> Changes in v3:
>   - Specified 'additionalProperties: false' within the parent MFD node and all
>     child nodes ("keys", "hall-switch-north/south" and "pwm")
>   - Defined the "hall-switch-north/south" child nodes unconditionally and then
>     inverted the subsequent if/then to filter them from devices for which that
>     functionality is unavailable
>   - Added Reviewed-by trailer
> 
> Changes in v2:
>   - Removed "prox" child node and moved "keys" and "pwm" child nodes to their
>     own bindings
>   - Replaced linux,fw-file property with more common firmware-name property
>   - Converted all bindings to YAML
> 
>  .../devicetree/bindings/input/iqs62x-keys.yaml     | 132 +++++++++++++++
>  Documentation/devicetree/bindings/mfd/iqs62x.yaml  | 179 +++++++++++++++++++++
>  .../devicetree/bindings/pwm/iqs620a-pwm.yaml       |  32 ++++
>  3 files changed, 343 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/input/iqs62x-keys.yaml
>  create mode 100644 Documentation/devicetree/bindings/mfd/iqs62x.yaml
>  create mode 100644 Documentation/devicetree/bindings/pwm/iqs620a-pwm.yaml

Applied, thanks.

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2020-02-24 11:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-16 23:32 [PATCH v5 0/7] Add support for Azoteq IQS620A/621/622/624/625 Jeff LaBundy
2020-02-16 23:32 ` [PATCH v5 1/7] dt-bindings: Add bindings " Jeff LaBundy
2020-02-24 11:14   ` Lee Jones [this message]
2020-02-16 23:32 ` [PATCH v5 2/7] mfd: Add support " Jeff LaBundy
2020-02-24 11:14   ` Lee Jones
2020-02-28  3:42     ` Jeff LaBundy
2020-03-02 12:04       ` Lee Jones
2020-03-02 14:11         ` Jeff LaBundy
2020-03-02 14:23           ` Uwe Kleine-König
2020-03-02 14:24           ` Lee Jones
2020-03-23  2:16             ` Jeff LaBundy
2020-03-24  8:16               ` Lee Jones
2020-02-16 23:32 ` [PATCH v5 3/7] input: keyboard: " Jeff LaBundy
2020-02-16 23:32 ` [PATCH v5 4/7] pwm: Add support for Azoteq IQS620A PWM generator Jeff LaBundy
2020-02-28  9:22   ` Uwe Kleine-König
2020-03-09  0:42     ` Jeff LaBundy
2020-02-16 23:32 ` [PATCH v5 5/7] iio: temperature: Add support for Azoteq IQS620AT temperature sensor Jeff LaBundy
2020-02-16 23:32 ` [PATCH v5 6/7] iio: light: Add support for Azoteq IQS621/622 ambient light sensors Jeff LaBundy
2020-02-16 23:32 ` [PATCH v5 7/7] iio: position: Add support for Azoteq IQS624/625 angle sensors Jeff LaBundy
2020-03-27  8:28 ` [GIT PULL] Immutable branch between MFD, IIO and Input due for the v5.7 merge window Lee Jones

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=20200224111422.GR3494@dell \
    --to=lee.jones@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jeff@labundy.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=u.kleine-koenig@pengutronix.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).