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 2/2] usb: gadget: composite: Draw 100mA current if not configured
Date: Thu, 23 Feb 2023 10:48:30 +0530 [thread overview]
Message-ID: <1677129510-10283-3-git-send-email-quic_prashk@quicinc.com> (raw)
In-Reply-To: <1677129510-10283-1-git-send-email-quic_prashk@quicinc.com>
Currently we don't change the current value if device isn't in
configured state. But the battery charging specification says,
the device can draw upto 100mA of current if its in unconfigured
state. Hence add a Vbus_draw work in composite_resume to draw
100mA if the device isn't configured.
Signed-off-by: Prashanth K <quic_prashk@quicinc.com>
---
drivers/usb/gadget/composite.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/usb/gadget/composite.c b/drivers/usb/gadget/composite.c
index fa7dd6c..147d278 100644
--- a/drivers/usb/gadget/composite.c
+++ b/drivers/usb/gadget/composite.c
@@ -2531,6 +2531,8 @@ void composite_resume(struct usb_gadget *gadget)
usb_gadget_clear_selfpowered(gadget);
usb_gadget_vbus_draw(gadget, maxpower);
+ } else {
+ usb_gadget_vbus_draw(gadget, 100);
}
cdev->suspended = 0;
--
2.7.4
next prev parent reply other threads:[~2023-02-23 5:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 5:18 [PATCH v1 0/2] Fix vbus draw of dwc3 gadget Prashanth K
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 ` Prashanth K [this message]
2023-02-23 7:33 ` [PATCH v1 2/2] usb: gadget: composite: Draw 100mA current if not configured 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-3-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