From: Prashanth K <quic_prashk@quicinc.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Thinh Nguyen" <Thinh.Nguyen@synopsys.com>,
"Jakob Koschel" <jakobkoschel@gmail.com>,
"Jó Ágila Bitsch" <jgilab@gmail.com>,
"Alan Stern" <stern@rowland.harvard.edu>
Cc: Pratham Pratap <quic_ppratap@quicinc.com>,
Jack Pham <quic_jackp@quicinc.com>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Prashanth K <quic_prashk@quicinc.com>
Subject: [PATCH v1 0/2] Fix vbus draw of dwc3 gadget
Date: Thu, 23 Feb 2023 10:48:28 +0530 [thread overview]
Message-ID: <1677129510-10283-1-git-send-email-quic_prashk@quicinc.com> (raw)
Currently dwc3 gadget processes the suspend interrupt event only
if the device is in configured state. But consider a case where
device is not configured and got suspend interrupt, in that case
our gadget would still use 100mA as composite_suspend didn't happen.
But battery charging specification (BC1.2) expects a downstream
device to draw less than 2.5mA when unconnected OR suspended.
And while resuming, the gadget can draw upto 100mA if its not
configured, but the current implementation of composite_resume
doesnt consider the case of unconfigured device. This series
addresses the above mentioned issues.
Prashanth K (2):
usb: dwc3: gadget: Change condition for processing suspend event
usb: gadget: composite: Draw 100mA current if not configured
drivers/usb/dwc3/gadget.c | 11 ++---------
drivers/usb/gadget/composite.c | 2 ++
2 files changed, 4 insertions(+), 9 deletions(-)
--
2.7.4
next reply other threads:[~2023-02-23 5:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 5:18 Prashanth K [this message]
2023-02-23 5:18 ` [PATCH v1 1/2] usb: dwc3: gadget: Change condition for processing suspend event Prashanth K
2023-02-23 5:18 ` [PATCH v1 2/2] usb: gadget: composite: Draw 100mA current if not configured Prashanth K
2023-02-23 7:33 ` Jack Pham
2023-02-23 8:22 ` Prashanth K
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=1677129510-10283-1-git-send-email-quic_prashk@quicinc.com \
--to=quic_prashk@quicinc.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=jakobkoschel@gmail.com \
--cc=jgilab@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=quic_jackp@quicinc.com \
--cc=quic_ppratap@quicinc.com \
--cc=stern@rowland.harvard.edu \
/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