From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: lianzhi chang <changlianzhi@uniontech.com>
Cc: linux-kernel@vger.kernel.org, dmitry.torokhov@gmail.com,
gregkh@linuxfoundation.org, jirislaby@kernel.org,
282827961@qq.com
Subject: Re: [PATCH v12] tty: Fix the keyboard led light display problem
Date: Fri, 5 Nov 2021 16:49:48 +0200 [thread overview]
Message-ID: <YYVEjMKfhnEMqQxD@smile.fi.intel.com> (raw)
In-Reply-To: <20211105134816.13982-1-changlianzhi@uniontech.com>
On Fri, Nov 05, 2021 at 09:48:16PM +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.
...
> Suggested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Not me, it's Dmitry who suggested the solution. Sorry I wasn't crystal clear
about this part.
...
> v11:
> Supplement the signature of the collaborator.
You have v12 in the subject...
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-11-05 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 13:48 [PATCH v12] tty: Fix the keyboard led light display problem lianzhi chang
2021-11-05 14:49 ` Andy Shevchenko [this message]
2021-11-05 22:36 ` Dmitry Torokhov
2021-11-08 1:33 ` 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=YYVEjMKfhnEMqQxD@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=282827961@qq.com \
--cc=changlianzhi@uniontech.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