From: Roger Quadros <rogerq@ti.com>
To: <myungjoo.ham@samsung.com>, <cw00.choi@samsung.com>
Cc: <linux-kernel@vger.kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>, <rogerq@ti.com>
Subject: [PATCH v3] extcon: usb-gpio: Don't miss event during suspend/resume
Date: Mon, 11 Apr 2016 17:04:45 +0300 [thread overview]
Message-ID: <570BAEFD.2050406@ti.com> (raw)
In-Reply-To: <57075F23.8080703@ti.com>
Pin state might have changed during suspend/resume while
our interrupts were disabled and if device doesn't support wakeup.
Scan for change during resume for such case.
Signed-off-by: Roger Quadros <rogerq@ti.com>
---
v3:
- use queue_delayed_work() instead of directly calling usb_extcon_detect_cable()
v2:
- only check for state change during resume if device wakeup is
drivers/extcon/extcon-usb-gpio.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/extcon/extcon-usb-gpio.c b/drivers/extcon/extcon-usb-gpio.c
index bc61d11..bad2159 100644
--- a/drivers/extcon/extcon-usb-gpio.c
+++ b/drivers/extcon/extcon-usb-gpio.c
@@ -185,6 +185,9 @@ static int usb_extcon_resume(struct device *dev)
int ret = 0;
enable_irq(info->id_irq);
+ if (!device_may_wakeup(dev))
+ queue_delayed_work(system_power_efficient_wq,
+ &info->wq_detcable, 0);
return ret;
}
--
2.5.0
next prev parent reply other threads:[~2016-04-11 14:04 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
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 ` Roger Quadros [this message]
2016-04-11 22:43 ` [PATCH v3] " 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=570BAEFD.2050406@ti.com \
--to=rogerq@ti.com \
--cc=cw00.choi@samsung.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.