From: Rob Herring <robh@kernel.org>
To: "Michal Vokáč" <michal.vokac@ysoft.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [RFC PATCH v2 1/4] dt-bindings: input: Add support for the MPR121 without interrupt line
Date: Thu, 13 Jun 2019 16:39:45 -0600 [thread overview]
Message-ID: <20190613223945.GA938@bogus> (raw)
In-Reply-To: <1558098773-47416-2-git-send-email-michal.vokac@ysoft.com>
On Fri, May 17, 2019 at 03:12:50PM +0200, Michal Vokáč wrote:
> Normally, the MPR121 controller uses separate interrupt line to notify
> the I2C host that a key was touched/released. To support platforms that
> can not use the interrupt line, polling of the MPR121 registers can be
> used.
'separate' from what?
>
> Signed-off-by: Michal Vokáč <michal.vokac@ysoft.com>
> ---
> Changes since v1:
> - Document the polled binding in the original file, do not create a new one.
> (Rob)
>
> Documentation/devicetree/bindings/input/mpr121-touchkey.txt | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/input/mpr121-touchkey.txt b/Documentation/devicetree/bindings/input/mpr121-touchkey.txt
> index b7c61ee5841b..97f55273d473 100644
> --- a/Documentation/devicetree/bindings/input/mpr121-touchkey.txt
> +++ b/Documentation/devicetree/bindings/input/mpr121-touchkey.txt
> @@ -1,9 +1,14 @@
> -* Freescale MPR121 Controllor
> +* Freescale MPR121 Controller
>
> Required Properties:
> -- compatible: Should be "fsl,mpr121-touchkey"
> +- compatible: Should be one of:
> + - "fsl,mpr121-touchkey" - MPR121 with interrupt line
> + - "fsl,mpr121-touchkey-polled" - MPR121 with polling
> - reg: The I2C slave address of the device.
> - interrupts: The interrupt number to the cpu.
> + In case of "fsl,mpr121-touchkey-polled" the interrupt
> + line is not used and hence the interrupts property is
> + not required.
Absence of the interrupts property is enough to determine polled mode
and you don't need a separate compatible string.
> - vdd-supply: Phandle to the Vdd power supply.
> - linux,keycodes: Specifies an array of numeric keycode values to
> be used for reporting button presses. The array can
> --
> 2.1.4
>
next prev parent reply other threads:[~2019-06-13 22:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 13:12 [RFC PATCH v2 0/4] Input: mpr121-polled: Add polled driver for MPR121 Michal Vokáč
2019-05-17 13:12 ` [RFC PATCH v2 1/4] dt-bindings: input: Add support for the MPR121 without interrupt line Michal Vokáč
2019-06-13 22:39 ` Rob Herring [this message]
2019-06-24 12:56 ` Michal Vokáč
2019-07-27 8:01 ` Dmitry Torokhov
2019-05-17 13:12 ` [RFC PATCH v2 2/4] Input: mpr121-polled: Add polling variant of the MPR121 touchkey driver Michal Vokáč
2019-05-17 13:12 ` [RFC PATCH v2 3/4] Input: mpr121-polled: Add write-through cache to detect corrupted registers Michal Vokáč
2019-05-17 13:12 ` [RFC PATCH v2 4/4] ARM: dts: imx6dl-yapp4: Enable MPR121 touch keypad on Hydra Michal Vokáč
2019-05-21 5:37 ` [RFC PATCH v2 0/4] Input: mpr121-polled: Add polled driver for MPR121 Dmitry Torokhov
2019-05-21 6:51 ` Michal Vokáč
2019-07-25 8:57 ` Dmitry Torokhov
2019-07-25 12:58 ` Michal Vokáč
2019-07-25 14:40 ` Dmitry Torokhov
2019-07-26 11:31 ` Michal Vokáč
2019-07-27 7:31 ` Dmitry Torokhov
2019-07-30 9:25 ` Michal Vokáč
2019-08-01 23:49 ` Dmitry Torokhov
2019-08-02 12:45 ` Michal Vokáč
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=20190613223945.GA938@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.vokac@ysoft.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).