linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Douglas Anderson <dianders@chromium.org>
Cc: linux-input@vger.kernel.org, hdegoede@redhat.com,
	robh@kernel.org, hans.verkuil@cisco.com, kamil@wypas.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: Add SW_PEN_INSERTED define
Date: Wed, 29 Jun 2016 10:08:20 -0700	[thread overview]
Message-ID: <20160629170820.GB35304@dtor-ws> (raw)
In-Reply-To: <1467133253-8075-1-git-send-email-dianders@chromium.org>

On Tue, Jun 28, 2016 at 10:00:53AM -0700, Douglas Anderson wrote:
> Some devices with a pen may have a switch that can be used to detect
> when the pen is inserted or removed to a slot on the device.  Let's add
> a define to the input event codes so that everyone can be on the same
> page for what event we should generate when the pen is inserted or
> removed.
> 
> In general the pen switch could be used by the software on the device to
> kick off any number of actions when the pen is inserted or removed.
> 
> Signed-off-by: Douglas Anderson <dianders@chromium.org>

Applied, thank you.

> ---
>  include/uapi/linux/input-event-codes.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/include/uapi/linux/input-event-codes.h b/include/uapi/linux/input-event-codes.h
> index 737fa32faad4..d6d071fc3c56 100644
> --- a/include/uapi/linux/input-event-codes.h
> +++ b/include/uapi/linux/input-event-codes.h
> @@ -780,6 +780,7 @@
>  #define SW_ROTATE_LOCK		0x0c  /* set = rotate locked/disabled */
>  #define SW_LINEIN_INSERT	0x0d  /* set = inserted */
>  #define SW_MUTE_DEVICE		0x0e  /* set = device disabled */
> +#define SW_PEN_INSERTED		0x0f  /* set = pen inserted */
>  #define SW_MAX			0x0f
>  #define SW_CNT			(SW_MAX+1)
>  
> -- 
> 2.8.0.rc3.226.g39d4020
> 

-- 
Dmitry

      reply	other threads:[~2016-06-29 17:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 17:00 [PATCH] Input: Add SW_PEN_INSERTED define Douglas Anderson
2016-06-29 17:08 ` Dmitry Torokhov [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=20160629170820.GB35304@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=dianders@chromium.org \
    --cc=hans.verkuil@cisco.com \
    --cc=hdegoede@redhat.com \
    --cc=kamil@wypas.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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).