From: sre@ring0.de (Sebastian Reichel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5 v2] input: tc3589x-keypad: support probing from device tree
Date: Tue, 12 Nov 2013 21:05:14 +0100 [thread overview]
Message-ID: <20131112200514.GA15413@earth.universe> (raw)
In-Reply-To: <CACRpkdb_bryGJo7CKGP5tj3RFGv=Gh+Q5m9ucVKqJ068tjPC2g@mail.gmail.com>
On Tue, Nov 12, 2013 at 06:06:49PM +0100, Linus Walleij wrote:
> On Tue, Nov 12, 2013 at 4:30 PM, Sebastian Reichel <sre@ring0.de> wrote:
> > On Tue, Nov 12, 2013 at 03:13:38PM +0100, Linus Walleij wrote:
>
> >> + plat->no_autorepeat = of_property_read_bool(np, "linux,no-autorepeat");
> >> + plat->enable_wakeup = of_property_read_bool(np, "linux,wakeup");
> >
> > There is currently discussion going on for the property name of
> > autorepeat:
> >
> > https://lkml.org/lkml/2013/11/11/680
>
> So this binding is documented for GPIO keys in:
> Documentation/devicetree/bindings/input/gpio-matrix-keypad.txt
>
> This is probably the most used binding as GPIO matrixes are
> not uncommon. But I don't know, yes it is a mess. (As usual.)
I could find two boards using "gpio-matrix-keypad" in the mainline
kernel and not a single instance of "linux,no-autorepeat":
arch $ grep "gpio-matrix-keypad" **/*.dts **/*.dtsi
arm/boot/dts/am335x-evm.dts: compatible = "gpio-matrix-keypad";
powerpc/boot/dts/ac14xx.dts: compatible = "gpio-matrix-keypad";
arch $ grep "autorepeat" **/*.dts **/*.dtsi
arch/arm/boot/dts/am335x-evm.dts: autorepeat;
arch/arm/boot/dts/ea3250.dts: autorepeat;
arch/arm/boot/dts/exynos4210-smdkv310.dts: linux,keypad-no-autorepeat;
arch/arm/boot/dts/exynos4412-origen.dts: linux,keypad-no-autorepeat;
arch/arm/boot/dts/exynos4412-smdk4412.dts: linux,keypad-no-autorepeat;
arch/arm/boot/dts/omap4-sdp.dts: linux,input-no-autorepeat;
arch/arm/boot/dts/spear1310-evb.dts: autorepeat;
arch/arm/boot/dts/spear1340-evb.dts: autorepeat;
arch/arm/boot/dts/spear300-evb.dts: autorepeat;
arch/arm/boot/dts/ste-stuib.dtsi: st,no-autorepeat;
-- Sebastian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131112/4a785fd2/attachment.sig>
next prev parent reply other threads:[~2013-11-12 20:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 14:13 [PATCH 4/5 v2] input: tc3589x-keypad: support probing from device tree Linus Walleij
2013-11-12 15:30 ` Sebastian Reichel
2013-11-12 17:06 ` Linus Walleij
2013-11-12 20:05 ` Sebastian Reichel [this message]
2013-11-12 20:11 ` Linus Walleij
2013-11-12 20:40 ` Sebastian Reichel
2013-11-13 14:24 ` Mark Rutland
2013-11-13 23:29 ` Sebastian Reichel
2013-11-14 11:12 ` Mark Rutland
2013-11-17 18:28 ` Pavel Machek
2013-12-02 11:37 ` Mark Rutland
2013-12-02 11:54 ` Pavel Machek
2013-12-02 12:08 ` Mark Rutland
2013-12-02 13:03 ` Pavel Machek
2013-11-17 18:28 ` Pavel Machek
2013-11-17 19:03 ` Sebastian Reichel
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=20131112200514.GA15413@earth.universe \
--to=sre@ring0.de \
--cc=linux-arm-kernel@lists.infradead.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).