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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 23 Nov 2017 20:24:05 +0800
From:   Chris Chiu <>
To:     Mika Westerberg <>
Cc:     Heikki Krogerus <>,
        Linus Walleij <>,,
        Linux Kernel <>,
        Linux Upstreaming Team <>
Subject: Re: [PATCH] pinctrl: intel: save HOSTSW_OWN register over suspend/resume

On Tue, Nov 21, 2017 at 8:04 PM, Mika Westerberg
<> wrote:
> On Tue, Nov 21, 2017 at 07:54:26PM +0800, Chris Chiu wrote:
>> Yup, I checked the value of the corresponded pin. It shows following before
>> suspend
>> pin 18 (GPIO_18) GPIO 0x40800102 0x00024075
>> Then after resume
>> pin 18 (GPIO_18) GPIO 0x40800102 0x00024075 [ACPI]
> OK, so ownership is changed to ACPI.
>> What else register do you suggest me to compare? The PADCFG2 is invalid
> It's fine APL does not have PADCFG2.
> Hmm, I don't understand how this can work in Windows either. The Windows
> people told me that they don't save and restore anything else than
> padcfg registers + ie. If the ownership is changed to ACPI it means you
> don't get interrupts anymore (only GPEs) and that applies to Windows as
> well.

Thanks for your confirmation. I've pushed this back to ASUS. They told me
there's a new official BIOS released, of course they don't know
whether if it helps
or not. I then upgraded it and the problem is gone. So it's truly a
BIOS but as you
said. Thanks for your help.


Powered by blists - more mailing lists