linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: The Cheaterman <the.cheaterman@gmail.com>
To: linux-input@vger.kernel.org
Subject: Re: [PATCH] HID: hid-input: avoid splitting keyboard, system and consumer controls
Date: Tue, 8 Feb 2022 23:26:35 +0100	[thread overview]
Message-ID: <CAOpBwpxyDJsqTrwRq-d0pmSGibcgiDf+-EeOMtQ=o8KfUU4beg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 453 bytes --]

Hello,

This breaks userspace. Now XkbLayout in xorg.conf.d is ignored for my
keyboard 0d62:3740 Darfon Electronics Corp. (built into my laptop)

Attached a simple patch that fixes the issue. Obviously, a revert is
probably a better idea ; or even better yet, do the part that was kept
aside to "keep the code simple".

Given this is happening on a consumer laptop (Alienware m15 R6), I'm
probably not the only one with this issue.

Thanks for reading.

[-- Attachment #2: 0001-fix-keyboard-layout.patch --]
[-- Type: text/x-patch, Size: 596 bytes --]

--- a/hid-input.c	2022-02-08 22:56:10.850000022 +0100
+++ b/hid-input.c	2022-02-08 22:56:15.737021611 +0100
@@ -1904,16 +1904,6 @@
 	list_for_each_entry(hidinput, &hid->inputs, list) {
 		if (hidinput->application == report->application)
 			return hidinput;
-
-		/*
-		 * Keep SystemControl and ConsumerControl applications together
-		 * with the main keyboard, if present.
-		 */
-		if ((report->application == HID_GD_SYSTEM_CONTROL ||
-		     report->application == HID_CP_CONSUMER_CONTROL) &&
-		    hidinput->application == HID_GD_KEYBOARD) {
-			return hidinput;
-		}
 	}
 
 	return NULL;

             reply	other threads:[~2022-02-08 22:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 22:26 The Cheaterman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-01-14  6:24 [PATCH] HID: hid-input: avoid splitting keyboard, system and consumer controls Dmitry Torokhov
2021-01-14  9:23 ` Benjamin Tissoires
2021-01-14 18:43   ` Dmitry Torokhov
2021-01-15  4:44 ` Peter Hutterer
2021-02-02 10:15 ` Jiri Kosina

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='CAOpBwpxyDJsqTrwRq-d0pmSGibcgiDf+-EeOMtQ=o8KfUU4beg@mail.gmail.com' \
    --to=the.cheaterman@gmail.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).