From: gregkh <gregkh@linuxfoundation.org>
To: "changlianzhi@uniontech.com" <changlianzhi@uniontech.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"dmitry.torokhov" <dmitry.torokhov@gmail.com>,
jirislaby <jirislaby@kernel.org>,
"andriy.shevchenko" <andriy.shevchenko@linux.intel.com>,
linux-input <linux-input@vger.kernel.org>,
282827961 <282827961@qq.com>
Subject: Re: [PATCH] input&tty: Fix the keyboard led light display problem
Date: Thu, 14 Oct 2021 15:21:51 +0200 [thread overview]
Message-ID: <YWgu71RP4ERZYjCy@kroah.com> (raw)
In-Reply-To: <616827d8.1c69fb81.75aa0.eea0SMTPIN_ADDED_BROKEN@mx.google.com>
On Thu, Oct 14, 2021 at 12:50:31PM +0800, changlianzhi@uniontech.com wrote:
> Subject: [PATCH] input&tty: Fix the keyboard led light display problem
>
>
> Switching from the desktop environment to the tty environment,
>
>
>
> the state of the keyboard led lights and the state of the keyboard
>
>
>
> lock are inconsistent. This is because the attribute kb->kbdmode
>
>
>
> of the tty bound in the desktop environment (xorg) is set to
>
>
>
> VC_OFF, which causes the ledstate and kb->ledflagstate
>
>
>
> values of the bound tty to always be 0, which causes the switch
>
>
>
> from the desktop When to the tty environment, the LED light
>
>
>
> status is inconsistent with the keyboard lock status.
>
>
>
>
>
>
>
> Signed-off-by: lianzhi chang <changlianzhi@uniontech.com>
>
>
>
> ---
>
>
>
> drivers/input/input.c | 7 ++++++-
>
>
>
> drivers/tty/vt/keyboard.c | 30 +++++++++++++++++++++++++++++-
>
>
>
> include/linux/kbd_kern.h | 2 ++
>
>
>
> 3 files changed, 37 insertions(+), 2 deletions(-)
>
>
>
>
>
>
>
> diff --git a/drivers/input/input.c b/drivers/input/input.c
>
>
>
> index ccaeb2426385..43c09700bf68 100644
>
>
>
> --- a/drivers/input/input.c
>
>
>
> +++ b/drivers/input/input.c
>
>
>
> @@ -25,6 +25,7 @@
>
>
>
> #include <linux/rcupdate.h>
>
>
>
> #include "input-compat.h"
>
>
>
> #include "input-poller.h"
>
>
>
> +#include <linux/kbd_kern.h>
>
>
>
> MODULE_AUTHOR("Vojtech Pavlik <vojtech@suse.cz>");
>
>
>
> MODULE_DESCRIPTION("Input core");
>
>
>
> @@ -472,8 +473,12 @@ void input_inject_event(struct input_handle *handle,
>
>
>
> rcu_read_lock();
>
>
>
> grab = rcu_dereference(dev->grab);
>
>
>
> - if (!grab || grab == handle)
>
>
>
> + if (!grab || grab == handle) {
>
>
>
> input_handle_event(dev, type, code, value);
>
>
>
> +
>
>
>
> + if (type == EV_LED && code < LED_SCROLLL)
>
>
>
> + update_value_ledstate(code, value);
>
>
>
> + }
>
>
>
> rcu_read_unlock();
>
>
>
> spin_unlock_irqrestore(&dev->event_lock, flags);
>
>
>
> diff --git a/drivers/tty/vt/keyboard.c b/drivers/tty/vt/keyboard.c
>
>
>
> index c7fbbcdcc346..0240915cdfef 100644
>
>
>
> --- a/drivers/tty/vt/keyboard.c
>
>
>
> +++ b/drivers/tty/vt/keyboard.c
>
>
>
> @@ -1140,6 +1140,31 @@ static unsigned char getledstate(void)
>
>
>
> return ledstate & 0xff;
>
>
>
> }
>
>
>
> +void update_value_ledstate(unsigned int flag, unsigned int value)
>
>
>
> +{
>
>
>
> + unsigned int bit;
>
>
>
> +
>
>
>
> + switch (flag) {
>
>
>
> + case LED_NUML:
>
>
>
> + bit = VC_NUMLOCK;
>
>
>
> + break;
>
>
>
> + case LED_CAPSL:
>
>
>
<snip>
Something went very wrong with this patch submission :(
Please fix up your email client and try again, or just use 'git
send-email' directly, as that should be all that you need here.
thanks,
greg k-h
next prev parent reply other threads:[~2021-10-14 13:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 8:53 [PATCH] input&tty: Fix the keyboard led light display problem lianzhi chang
[not found] ` <616827d8.1c69fb81.75aa0.eea0SMTPIN_ADDED_BROKEN@mx.google.com>
2021-10-14 13:21 ` gregkh [this message]
[not found] <35696980-2a55-c5c1-3fa9-eadf251dcdde@uniontech.com>
2021-10-15 13:06 ` Andy Shevchenko
[not found] <20211015083613.7429-1-changlianzhi@uniontech.com>
2021-10-15 8:41 ` Greg KH
[not found] ` <616942b2.1c69fb81.dfbff.25afSMTPIN_ADDED_BROKEN@mx.google.com>
2021-10-15 10:16 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2021-10-15 8:37 lianzhi chang
[not found] <61693925.1c69fb81.a058.27f2SMTPIN_ADDED_BROKEN@mx.google.com>
2021-10-15 8:25 ` Greg KH
2021-10-15 6:45 lianzhi chang
2021-10-15 6:52 ` Greg KH
[not found] ` <616934f3.1c69fb81.59ff6.49d9SMTPIN_ADDED_BROKEN@mx.google.com>
2021-10-15 8:04 ` Greg KH
2021-10-15 1:20 lianzhi chang
[not found] <20211014071627.23256-1-changlianzhi@uniontech.com>
2021-10-14 7:34 ` Greg KH
2021-10-14 15:13 ` Andy Shevchenko
2021-10-14 14:55 ` Jiri Slaby
2021-10-14 18:20 ` Dmitry Torokhov
2021-10-14 7:20 lianzhi chang
[not found] <20211014040508.8367-1-changlianzhi@uniontech.com>
2021-10-14 4:12 ` Jiri Slaby
[not found] <20211014030836.30612-1-changlianzhi@uniontech.com>
2021-10-14 4:12 ` Jiri Slaby
2021-10-14 4:06 lianzhi chang
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=YWgu71RP4ERZYjCy@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=282827961@qq.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=changlianzhi@uniontech.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jirislaby@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).