linux-kernel - [PATCH 0/1] pinctrl: amd: pinctrl: amd: disable and mask interrupts on probe

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>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20211001161714.2053597-1-nakato@nakato.io>
Date:   Sat,  2 Oct 2021 02:17:13 +1000
From:   Sachi King <nakato@...ato.io>
To:     linux-gpio@...r.kernel.org, basavaraj.natikar@....com
Cc:     linux-kernel@...r.kernel.org, Sachi King <nakato@...ato.io>
Subject: [PATCH 0/1] pinctrl: amd: pinctrl: amd: disable and mask interrupts on probe

On a Microsoft Surface Laptop 4, I've found that the GPIO controller is
preconfigured with a number of interrupts.  I'm not sure if this is
device specific, in which case I could propose a quirk, or a more
general issue.  Prior to https://git.kernel.org/torvalds/c/acd47b9f28e5
which will be in 5.15, this device exhibited failed resumes that would
result in high power consumption and no reliable way to resume the
device.  Following that patch the device exhibits spurious wakeups.

As far as I can tell interrupts should be disabled and masked as a
default state, so ensuring this is the initial state should be safe as a
default action.

Sachi King (1):
  pinctrl: amd: disable and mask interrupts on probe

 drivers/pinctrl/pinctrl-amd.c | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)

-- 
2.33.0