[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <etxvdq6rex3cbloonveshekt2gpcmjbq2ynbx6peieup7x6uxt@agvcndnybli7>
Date: Sat, 15 Nov 2025 10:35:39 +0800
From: Xu Yang <xu.yang_2@....com>
To: MyungJoo Ham <myungjoo.ham@...sung.com>
Cc: "krzk@...nel.org" <krzk@...nel.org>,
Chanwoo Choi <cw00.choi@...sung.com>, "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
Hi MyungJoo,
On Sat, Nov 15, 2025 at 10:01:45AM +0900, MyungJoo Ham wrote:
> >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?
Yes, it's ok because the mutex lock will protect it and if irq-handler
is invoked firstly, ptn5150_resume() will just read the status registers
and return soon since no pending events.
>
> Acked-by: MyungJoo Ham <myungjoo.ham@...sung.com>
Thanks,
Xu Yang
>
> >
> >Signed-off-by: Xu Yang <xu.yang_2@....com>
> >---
> > drivers/extcon/extcon-ptn5150.c | 14 ++++++++++++++
> > 1 file changed, 14 insertions(+)
> >
Powered by blists - more mailing lists