From: Bernhard Walle <bernhard@bwalle.de>
To: Peter Chen <peter.chen@nxp.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: chipidea: Fix missing resume call after suspend
Date: Tue, 25 Apr 2017 15:19:00 +0200 (CEST) [thread overview]
Message-ID: <945599000.34345.1493126340352@office.mailbox.org> (raw)
In-Reply-To: <20170425081403.GA873@b29397-desktop>
Hi Peter,
> Peter Chen <peter.chen@nxp.com> hat am 25. April 2017 um 10:14 geschrieben:
>
> Since you unplug the cable first, and plug in again. The driver will
> treat it as connection but not resume event. You may use
> /sys/class/udc/ci_hdrc.0/state to get udc's connection, eg "not attached"
> or other states to indicate connection.
Thanks for the hint. This works for me.
Regards,
Bernhard
prev parent reply other threads:[~2017-04-25 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 10:10 [PATCH] usb: chipidea: Fix missing resume call after suspend Bernhard Walle
2017-04-24 3:51 ` Peter Chen
2017-04-24 13:25 ` Bernhard Walle
2017-04-25 8:14 ` Peter Chen
2017-04-25 13:19 ` Bernhard Walle [this message]
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=945599000.34345.1493126340352@office.mailbox.org \
--to=bernhard@bwalle.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@nxp.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).