From: Chanwoo Choi <cw00.choi@samsung.com>
To: Roger Quadros <rogerq@ti.com>, myungjoo.ham@samsung.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] extcon: usb-gpio: Don't miss event during suspend/resume
Date: Fri, 08 Apr 2016 08:39:00 +0900 [thread overview]
Message-ID: <5706EF94.6010903@samsung.com> (raw)
In-Reply-To: <1459951299-20578-1-git-send-email-rogerq@ti.com>
On 2016년 04월 06일 23:01, Roger Quadros wrote:
> Pin state might have changed during suspend/resume while
> our interrupts were disabled. Scan for change during resume.
>
> Signed-off-by: Roger Quadros <rogerq@ti.com>
> ---
> drivers/extcon/extcon-usb-gpio.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/extcon/extcon-usb-gpio.c b/drivers/extcon/extcon-usb-gpio.c
> index 2b2fecf..20175ec 100644
> --- a/drivers/extcon/extcon-usb-gpio.c
> +++ b/drivers/extcon/extcon-usb-gpio.c
> @@ -192,6 +192,7 @@ static int usb_extcon_resume(struct device *dev)
> }
>
> enable_irq(info->id_irq);
> + usb_extcon_detect_cable(&info->wq_detcable.work);
If interrupt is using as wakeup source/irq,
after wake-up from suspend state, the interrupt handler will be handled.
But, if interrupt is not used for wakeup source/irq,
As your patch, we need to check the state on resume().
So, I think you need more condition to check the interrupt is whether wakeup source or not.
Thanks,
Chanwoo CHoi
next prev parent reply other threads:[~2016-04-07 23:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 14:01 [PATCH] extcon: usb-gpio: Don't miss event during suspend/resume Roger Quadros
2016-04-07 23:39 ` Chanwoo Choi [this message]
2016-04-08 7:34 ` [PATCH v2] " Roger Quadros
2016-04-11 0:31 ` Chanwoo Choi
2016-04-11 8:37 ` Grygorii Strashko
2016-04-11 11:12 ` Chanwoo Choi
2016-04-11 11:39 ` Roger Quadros
2016-04-11 13:17 ` Chanwoo Choi
2016-04-11 14:02 ` Roger Quadros
2016-04-11 14:04 ` [PATCH v3] " Roger Quadros
2016-04-11 22:43 ` Chanwoo Choi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5706EF94.6010903@samsung.com \
--to=cw00.choi@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=rogerq@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).