linux-kernel - RE: [PATCH] extcon: ptn5150: handle pending IRQ events during system resume

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

Message-ID: <20251115010145epcms1p5b7fccdadb889d9b88f447a73c9a8a7b0@epcms1p5>
Date: Sat, 15 Nov 2025 10:01:45 +0900
From: MyungJoo Ham <myungjoo.ham@...sung.com>
To: Xu Yang <xu.yang_2@....com>, "krzk@...nel.org" <krzk@...nel.org>,
	Chanwoo Choi <cw00.choi@...sung.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"imx@...ts.linux.dev" <imx@...ts.linux.dev>
Subject: RE: [PATCH] extcon: ptn5150: handle pending IRQ events during
 system resume

>When the system is suspended and ptn5150 wakeup interrupt is disabled,
>any changes on ptn5150 will only be record in interrupt status
>registers and won't fire an IRQ since its trigger type is falling
>edge. So the HW interrupt line will keep at low state and any further
>changes won't trigger IRQ anymore. To fix it, this will schedule a
>work to check whether any IRQ are pending and handle it accordingly.

It is ok call ptn5150_irq_work() anytime during resume even if
irq-handler is invoked right before ptn5150_resume(), right?

Acked-by: MyungJoo Ham <myungjoo.ham@...sung.com>

>
>Signed-off-by: Xu Yang <xu.yang_2@....com>
>---
> drivers/extcon/extcon-ptn5150.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>