From: Lee Jones <lee.jones@linaro.org>
To: S Twiss <stwiss.opensource@diasemi.com>
Cc: DEVICETREE <devicetree@vger.kernel.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
LINUXINPUT <linux-input@vger.kernel.org>,
LINUXKERNEL <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Pawel Moll <pawel.moll@arm.com>,
RTCLINUX <rtc-linux@googlegroups.com>,
Rob Herring <robh+dt@kernel.org>,
David Dajun Chen <david.chen@diasemi.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Support Opensource <support.opensource@diasemi.com>
Subject: Re: [PATCH V2 3/3] devicetree: da9062: Add device tree bindings for DA9062 OnKey
Date: Thu, 23 Jul 2015 16:07:11 +0100 [thread overview]
Message-ID: <20150723150711.GI3436@x1> (raw)
In-Reply-To: <f3630d64fd819832dc2d0925b49c1dca9b11644b.1437399438.git.stwiss.opensource@diasemi.com>
On Mon, 20 Jul 2015, S Twiss wrote:
> From: S Twiss <stwiss.opensource@diasemi.com>
>
> Add device tree bindings for the DA9062 OnKey driver component
>
> Signed-off-by: Steve Twiss <stwiss.opensource@diasemi.com>
>
> ---
> Checks performed with linux-next/next-20150708/scripts/checkpatch.pl
> da9062.txt total: 0 errors, 0 warnings, 97 lines checked
> This patch applies against linux-next and next-20150708
>
>
> Documentation/devicetree/bindings/mfd/da9062.txt | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/da9062.txt b/Documentation/devicetree/bindings/mfd/da9062.txt
> index 5765ed9..7752093 100644
> --- a/Documentation/devicetree/bindings/mfd/da9062.txt
> +++ b/Documentation/devicetree/bindings/mfd/da9062.txt
> @@ -5,6 +5,7 @@ DA9062 consists of a large and varied group of sub-devices:
> Device Supply Names Description
> ------ ------------ -----------
> da9062-regulator : : LDOs & BUCKs
> +da9062-onkey : : On Key
> da9062-watchdog : : Watchdog Timer
>
> ======
> @@ -41,6 +42,18 @@ Sub-nodes:
> Documentation/devicetree/bindings/regulator/regulator.txt
>
>
> +- onkey : This node defines the OnKey settings for controlling the key
> + functionality of the device. The node should contain the compatible property
> + with the value "dlg,da9063-onkey".
> +
> + Optional onkey properties:
> +
> + - dlg,disable-key-power : Disable power-down using a long key-press. If this
> + entry exists the OnKey driver will remove support for the KEY_POWER key
> + press. If this entry does not exist then by default the key-press
> + triggered power down is enabled and the OnKey will support both KEY_POWER
> + and KEY_SLEEP.
Child driver specifics should be separated out into other SS'
documents, in this case ../input.
> - watchdog: This node defines the settings for the watchdog driver associated
> with the DA9062 PMIC. The compatible = "dlg,da9062-watchdog" should be added
> if a node is created.
> @@ -59,6 +72,11 @@ Example:
> compatible = "dlg,da9062-watchdog";
> };
>
> + onkey {
> + compatible = "dlg,da9063-onkey";
> + dlg,disable-key-power;
> + };
> +
> regulators {
> DA9062_BUCK1: buck1 {
> regulator-name = "BUCK1";
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-07-23 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 13:37 [PATCH V2 0/3] da9062: Add DA9062 OnKey support using the existing DA9063 OnKey driver S Twiss
2015-07-20 13:37 ` [PATCH V2 1/3] mfd: da9062: Support for the DA9063 OnKey in the DA9062 core S Twiss
2015-07-23 15:07 ` Lee Jones
2015-07-20 13:37 ` [PATCH V2 2/3] onkey: da9063: Add DA9062 OnKey capability to DA9063 OnKey driver S Twiss
2015-07-20 13:37 ` [PATCH V2 3/3] devicetree: da9062: Add device tree bindings for DA9062 OnKey S Twiss
2015-07-23 15:07 ` Lee Jones [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=20150723150711.GI3436@x1 \
--to=lee.jones@linaro.org \
--cc=david.chen@diasemi.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=sameo@linux.intel.com \
--cc=stwiss.opensource@diasemi.com \
--cc=support.opensource@diasemi.com \
/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).