public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: lianzhi chang <changlianzhi@uniontech.com>
Cc: "dmitry.torokhov" <dmitry.torokhov@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	jirislaby <jirislaby@kernel.org>, 282827961 <282827961@qq.com>
Subject: Re: [PATCH v14] tty: Fix the keyboard led light display problem
Date: Thu, 25 Nov 2021 13:40:21 +0200	[thread overview]
Message-ID: <YZ92JaKnUbXb0shZ@smile.fi.intel.com> (raw)
In-Reply-To: <tencent_5573CD56296D5E2F4C59A664@qq.com>

On Thu, Nov 25, 2021 at 10:33:23AM +0800, lianzhi chang wrote:
> > > On Mon, Nov 08, 2021 at 01:51:39PM +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
> 
> > > We know that Xorg sets kbdmode mode to VC_OFF, but it does not mean that
> > > you can say for sure that it is Xorg instance that controls a VT simply
> > > by observing kb->kbdmode. There may be something else entirely. That is
> > > why you want drivers/tty/vt/keyboard.c to reset LEDs and leave it to
> > > whoever is controlling VT to set them to something else if it is
> > > desired.
> 
> > Does this mean let me change the description information? Or is the
> > judgment of VC_OFF in patch incorrect?
> > The setup method of Xorg mentioned here is just to describe a process
> > in which I found the problem;
> > My understanding is that when the mode of kbdmode is set to VC_OFF,
> > VT shouldn't interfere with the state of the keyboard light, right? This is
> > how functions such as kbd_keycode() are implemented.
> > When VT is switched, if the VT mode is VC_OFF, there is also no need
> > to set the state of the keyboard light. I think this is reasonable.
> 
> > > > > 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.

> Hi friends, how is this patch progressing now, do I need to modify it further?

At least I have told you already twice that I'm not the guy who suggested this
solution. Others seem gave you other comments.

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2021-11-25 11:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-08  5:51 [PATCH v14] tty: Fix the keyboard led light display problem lianzhi chang
2021-11-08  9:37 ` Andy Shevchenko
2021-11-10  6:41 ` Dmitry Torokhov
2021-11-10  7:26   ` lianzhi chang
2021-11-25  2:33     ` lianzhi chang
2021-11-25 11:40       ` 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=YZ92JaKnUbXb0shZ@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