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 v13] tty: Fix the keyboard led light display problem
Date: Mon, 8 Nov 2021 11:36:21 +0200 [thread overview]
Message-ID: <YYjvlb0taamSTElN@smile.fi.intel.com> (raw)
In-Reply-To: <20211108054510.4680-1-changlianzhi@uniontech.com>
On Mon, Nov 08, 2021 at 01:45:10PM +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>
Shouldn't be here. I haven't suggested the current implementation.
What I had done is proposed changes to one of the previous versions
which was wrong from design perspective and got rejected.
...
> + /* Xorg will bind a tty, the kb->kbdmode of this tty will be set to
> + * VC_OFF, and this tty will no longer set the keyboard light. If
> + * there is no such restriction, when switching from other tty to
> + * Xorg-bound tty, the tty will set the keyboard light, which is
> + * unreasonable
> + */
trailing whitespaces. Had you run checkpatch?
Even Git warns about them when you do `git commit ...`
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2021-11-08 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 5:45 [PATCH v13] tty: Fix the keyboard led light display problem lianzhi chang
2021-11-08 9:36 ` Andy Shevchenko [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=YYjvlb0taamSTElN@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.