[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1677142665-8686-1-git-send-email-quic_prashk@quicinc.com>
Date: Thu, 23 Feb 2023 14:27:43 +0530
From: Prashanth K <quic_prashk@...cinc.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Thinh Nguyen <Thinh.Nguyen@...opsys.com>,
Jakob Koschel <jakobkoschel@...il.com>,
Jó Ágila Bitsch <jgilab@...il.com>,
Alan Stern <stern@...land.harvard.edu>
CC: Pratham Pratap <quic_ppratap@...cinc.com>,
Jack Pham <quic_jackp@...cinc.com>,
<linux-usb@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Prashanth K <quic_prashk@...cinc.com>
Subject: [PATCH v2 0/2] Fix vbus draw of dwc3 gadget
Changes in v2
- Added min() calculation against CONFIG_USB_GADGET_VBUS_DRAW in case
of unconfigured state.
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
doesn't 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 | 3 +++
2 files changed, 5 insertions(+), 9 deletions(-)
--
2.7.4
Powered by blists - more mailing lists