From: "lianzhi chang" <changlianzhi@uniontech.com>
To: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"dmitry.torokhov" <dmitry.torokhov@gmail.com>,
"Greg KH" <gregkh@linuxfoundation.org>,
jirislaby <jirislaby@kernel.org>, 282827961 <282827961@qq.com>
Subject: Re: [PATCH v10] tty: Fix the keyboard led light display problem
Date: Fri, 5 Nov 2021 21:38:13 +0800 [thread overview]
Message-ID: <tencent_0E22777E5505E7C27FF412EB@qq.com> (raw)
In-Reply-To: <YYUoWJWbPpK079/d@smile.fi.intel.com>
On Fri, Nov 05, 2021 at 08:24:43PM +0800, lianzhi chang wrote:
> > 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.
> > In order to ensure that the keyboard LED lights are displayed
> > normally during the VT switching process, when the VT is
> > switched, the current VT LED configuration is forced to be issued.
> >
> > Signed-off-by: lianzhi chang <changlianzhi@uniontech.com>
> > ---
> > v10:
> > The led state of the input device is no longer synchronized to
> > ledstate, and the related code is deleted. The current plan is
> > changed to: when the VT is switched, the LED state saved by the
> > current VT is forced to be issued.
> >
> Shouldn't you add a Suggested-by tag?
Oh, sorry, I was negligent, I will add it right away.
Thanks.
--
lianzhi chang
prev parent reply other threads:[~2021-11-05 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 12:24 lianzhi chang
2021-11-05 12:49 ` Andy Shevchenko
2021-11-05 13:38 ` lianzhi chang [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=tencent_0E22777E5505E7C27FF412EB@qq.com \
--to=changlianzhi@uniontech.com \
--cc=282827961@qq.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@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
all inboxes | Powered by JetHome®