All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
Cc: "João Paulo Rechi Vita" <jprvita@endlessm.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	"Platform Driver" <platform-driver-x86@vger.kernel.org>,
	"Linux Upstreaming Team" <linux@endlessm.com>,
	"João Paulo Rechi Vita" <jprvita@gmail.com>
Subject: Re: X450LCP lost abillity to turn the screen off
Date: Tue, 12 Feb 2019 12:30:13 +0200	[thread overview]
Message-ID: <CAHp75Vdbtou6Y0+He9f70kTRYyDiXR=jBATgTS8LK+SWXwTeUg@mail.gmail.com> (raw)
In-Reply-To: <e1be4724-38df-ac86-551c-7cfaf8e50b19@gmail.com>

On Tue, Feb 12, 2019 at 4:31 AM Marcos Paulo de Souza
<marcos.souza.org@gmail.com> wrote:
> On 2/11/19 5:14 PM, João Paulo Rechi Vita wrote:
> > Hello Marcos,
> > On Sun, Feb 10, 2019 at 5:05 PM Marcos Paulo de Souza
> > <marcos.souza.org@gmail.com> wrote:

> > You can check what is being sent by the kernel with evtest, and what
> > is being sent by X with "xinput test <device id>" (and you can find
> > the device id with "xinput list"). And you can re-map it without
> > having to rebuild the kernel using udev's hwdb. But simply re-mapping
> > should not change anything, since userspace does not act on
> > KEY_DISPLAYTOGGLE / KEY_DISPLAY_OFF. If you want to switch back to the
> > old behavior you need to revert "78f3ac76d9e5 platform/x86: asus-wmi:
> > Tell the EC the OS will handle the display off hotkey".
>
> I tried reverting the patch and only recompiling/reinstalling the
> platform/x86 modules, but the problem still happens. My next step will
> be testing agains't 4.20, since my machine was working with 4.12, so I
> might try the major releases first.

When you are going to try older releases, it would be nice to see if
LTS kernels (v4.14.y, v4.19.y from Linux stable tree [1]) behave
differently

[1]: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/

-- 
With Best Regards,
Andy Shevchenko

  reply	other threads:[~2019-02-12 10:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-10 19:24 X450LCP lost abillity to turn the screen off Marcos Paulo de Souza
2019-02-10 23:45 ` Andy Shevchenko
2019-02-11  1:06   ` Marcos Paulo de Souza
2019-02-11 19:14     ` João Paulo Rechi Vita
2019-02-12  2:31       ` Marcos Paulo de Souza
2019-02-12 10:30         ` Andy Shevchenko [this message]
2019-02-12 16:30         ` João Paulo Rechi Vita
2019-02-13 21:46           ` Marcos Paulo de Souza
2019-02-23  3:49             ` Marcos Paulo de Souza

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='CAHp75Vdbtou6Y0+He9f70kTRYyDiXR=jBATgTS8LK+SWXwTeUg@mail.gmail.com' \
    --to=andy.shevchenko@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=jprvita@endlessm.com \
    --cc=jprvita@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@endlessm.com \
    --cc=marcos.souza.org@gmail.com \
    --cc=platform-driver-x86@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.