linux-kernel - Re: [git pull] Input updates for v6.1-rc5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3ca60b3e-4f7e-5a31-b74e-e4f01e576430@leemhuis.info>
Date:   Sat, 24 Dec 2022 09:15:54 +0100
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Aman Dhoot <amandhoot12@...il.com>
Cc:     linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
        Dmitry Torokhov <dmitry.torokhov@...il.com>
Subject: Re: [git pull] Input updates for v6.1-rc5

[CCing Dmitry]

Hi, this is your Linux kernel regression tracker.

On 24.12.22 08:49, Aman Dhoot wrote:
> If I use synaptics touchpad in legacy PS/2 mode.keyboard and touchpad
> stop working randomly because of TLP, if I uninstall tlp it resolves
> the keyboard touchpad stops working randomly issue. But I see good
> battery life in my system using tlp by switching touchpad from legacy
> PS/2 mode to RMI mode resolves the problem. this way i can use tlp and
> keyboard touchpad works without any problem.
> 
> In my dmesg log I don't have msg "psmouse serio1: synaptics: SMbus
> companion is not ready yet".

Well, if I got this right the situation is like this: your change
ac5408991ea6 ("Input: synaptics - switch touchpad on HP Laptop
15-da3001TU to RMI mode") breaks things for some users and hence will be
reverted per the "no regressions rule" (
https://docs.kernel.org/process/handling-regressions.html ).

To get this reapplied someone needs to work with those people that are
affected by the regression to ensure this continue working if the
touchpad is in RMI mode (maybe it depends on the BIOS, the revsition,
the kernel config, or something else). IOW: a better change is needed
that doesn't break things for others. If that's not possible maybe there
is some other solution for you. Is there maybe a kernel parameter you
can apply to switch the device to RMI mode on your machine?

HTH, Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker'
hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.