linux-kernel - Re: [PATCH] pinctrl: intel: Clear interrupt status in unmask callback

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Thu, 25 Apr 2019 13:16:25 +0800
From:   Kai Heng Feng <kai.heng.feng@...onical.com>
To:     hotwater438@...anota.com
Cc:     Mika Westerberg <mika.westerberg@...ux.intel.com>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Linus Walleij <linus.walleij@...aro.org>,
        Hdegoede <hdegoede@...hat.com>,
        Linux Gpio <linux-gpio@...r.kernel.org>,
        Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] pinctrl: intel: Clear interrupt status in unmask callback

at 9:49 PM, <hotwater438@...anota.com> <hotwater438@...anota.com> wrote:

> Hi. I did the suggested echo and, if I clearly understood, switched to  
> s2idle mode without deep-mode.
> For tests I use 4.19.28 on Debian-like system (Parrot OS).
>
> If the system defaults to use S2I, then it’s better to stick with it.
>
> Lots of ODM/OEM don’t really test S3.
> So S3 is the same as S2 but with deep mode enabled?
> The default switches to s2idle based on FADT flag and _DSM on relative  
> new kernels.
> Are those some SSDT flags?
> It actually sounds weird to me, why restarting touchpad after deep  
> suspend affects it work. I mean, if it starts sucessfully at boot, why it  
> doesn't after suspend? Can we debug it somehow?

Can you see if i2c_hid_hwreset() helps? Refer to [1] as an example.

Anyway, the resume issue is a different bug. If possible please merge this  
patch.

[1] https://lore.kernel.org/lkml/20190211070040.4569-1-jbroadus@gmail.com/

Kai-Heng

>
> Regards,
> Vladislav.
> Apr 23, 2019, 12:47 PM by kai.heng.feng@...onical.com:
> at 17:40, <hotwater438@...anota.com> <hotwater438@...anota.com> wrote:
> Hi. Thank's for a hint!
> So catting this file gives me next content:
> s2idle [deep]
>
> Which kernel version do you use?
>
>
> Most systems preload with Windows 8.1 should default to use s2idle.
>
> So I suppose I have s2idle with deep-mode available?
>
> I've tried to select deep by creating mem_sleep_default file, but I can't  
> (Permission error).
>
> Could you explain how do I switch suspend mode in Linux, if you know?
>
> # echo s2idle > /sys/power/mem_sleep
> And to be honest, I don't think that's a correct fix of touchpad problem.
>
>
>
> Can we somehow cut off the power by hands or send a signal to a system to  
> shut off a touchpad? Or there are no approaches like that?
>
> I don’t think it’s possible.
>
> Kai-Heng
>
> Regards,
> Vladislav.
>
>
> Apr 23, 2019, 12:08 PM by mika.westerberg@...ux.intel.com:
> On Tue, Apr 23, 2019 at 11:00:48AM +0200, hotwater438@...anota.com wrote:
> Hi.
>
> Honestly, I can't find any information about my acpi suspend type.
> There are no options in my BIOS to change it, and I can't determine
> which exactly I have. But I suppose I have a S3 because I have suspend
> issue.
>
> Can I somehow determine it in Linux? I did a research but found nothing
> on the internet.
>
> You can read the default mode from /sys/power/mem_sleep. "s2idle" means,
> well suspend-to-idle and "deep" means S3.