linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH v2] hid-input: Map unknown consumer page codes to KEY_UNKNOWN
Date: Tue, 21 Oct 2014 14:55:39 -0700	[thread overview]
Message-ID: <20141021215539.GF8609@dtor-ws> (raw)
In-Reply-To: <1413925860-3441-1-git-send-email-hdegoede@redhat.com>

On Tue, Oct 21, 2014 at 11:11:00PM +0200, Hans de Goede wrote:
> Currently unknown consumer page codes are ignored, which means that they
> cannot later be mapped from userspace using udev / hwdb. Map them to
> KEY_UNKNOWN, so that userspace can remap them for keyboards which
> make up their own consumer page codes.
> 
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>

I think this makes sense. Thanks Hans.

> 
> --
> Changes in v2: Use key_map_clear rather then key_map
> ---
>  drivers/hid/hid-input.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/hid/hid-input.c b/drivers/hid/hid-input.c
> index 2619f7f..a6e33d3 100644
> --- a/drivers/hid/hid-input.c
> +++ b/drivers/hid/hid-input.c
> @@ -856,7 +856,7 @@ static void hidinput_configure_usage(struct hid_input *hidinput, struct hid_fiel
>  		case 0x28b: map_key_clear(KEY_FORWARDMAIL);	break;
>  		case 0x28c: map_key_clear(KEY_SEND);		break;
>  
> -		default:    goto ignore;
> +		default: map_key_clear(KEY_UNKNOWN);
>  		}
>  		break;
>  
> -- 
> 2.1.0
> 

-- 
Dmitry

      reply	other threads:[~2014-10-21 21:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 21:11 [PATCH v2] hid-input: Map unknown consumer page codes to KEY_UNKNOWN Hans de Goede
2014-10-21 21:55 ` 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=20141021215539.GF8609@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-input@vger.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).