From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Grant Likely <grant.likely@linaro.org>
Subject: Re: [PATCH RESEND] input: dts: Add commonly used event types
Date: Fri, 28 Mar 2014 09:43:00 -0700 [thread overview]
Message-ID: <20140328164300.GB7582@core.coreip.homeip.net> (raw)
In-Reply-To: <1395165888-17434-1-git-send-email-shc_work@mail.ru>
On Tue, Mar 18, 2014 at 10:04:47PM +0400, Alexander Shiyan wrote:
> Patch adds commonly used event types (EV_KEY and EV_SW) to
> devicetree bindings header for input subsystem.
>
> Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
> ---
> include/dt-bindings/input/input.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/include/dt-bindings/input/input.h b/include/dt-bindings/input/input.h
> index 042e7b3..3a141d92 100644
> --- a/include/dt-bindings/input/input.h
> +++ b/include/dt-bindings/input/input.h
> @@ -9,6 +9,9 @@
> #ifndef _DT_BINDINGS_INPUT_INPUT_H
> #define _DT_BINDINGS_INPUT_INPUT_H
>
> +#define EV_KEY 0x01
> +#define EV_SW 0x05
> +
> #define KEY_RESERVED 0
> #define KEY_ESC 1
> #define KEY_1 2
> --
> 1.8.3.2
>
This I believe should go through device tree.
--
Dmitry
next prev parent reply other threads:[~2014-03-28 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 18:04 [PATCH RESEND] input: dts: Add commonly used event types Alexander Shiyan
2014-03-18 18:04 ` [PATCH v3 2/2] input: clps711x-keypad: dts: Add bindings documentation Alexander Shiyan
2014-03-28 16:43 ` Dmitry Torokhov
2014-03-28 16:43 ` Dmitry Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-26 5:37 [PATCH RESEND] input: dts: Add commonly used event types Alexander Shiyan
2014-05-14 18:08 ` Dmitry Torokhov
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=20140328164300.GB7582@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-input@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=shc_work@mail.ru \
/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).