<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/usb/dwc3/core.c, branch linux-5.17.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.17.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.17.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2022-05-09T07:16:13Z</updated>
<entry>
<title>usb: dwc3: core: Only handle soft-reset in DCTL</title>
<updated>2022-05-09T07:16:13Z</updated>
<author>
<name>Thinh Nguyen</name>
</author>
<published>2022-04-22T02:33:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9915ce17c420d594f99dd870a621949e5c9a6791'/>
<id>urn:sha1:9915ce17c420d594f99dd870a621949e5c9a6791</id>
<content type='text'>
commit f4fd84ae0765a80494b28c43b756a95100351a94 upstream.

Make sure not to set run_stop bit or link state change request while
initiating soft-reset. Register read-modify-write operation may
unintentionally start the controller before the initialization completes
with its previous DCTL value, which can cause initialization failure.

Fixes: f59dcab17629 ("usb: dwc3: core: improve reset sequence")
Cc: &lt;stable@vger.kernel.org&gt;
Signed-off-by: Thinh Nguyen &lt;Thinh.Nguyen@synopsys.com&gt;
Link: https://lore.kernel.org/r/6aecbd78328f102003d40ccf18ceeebd411d3703.1650594792.git.Thinh.Nguyen@synopsys.com
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>usb: dwc3: core: Fix tx/rx threshold settings</title>
<updated>2022-05-09T07:16:13Z</updated>
<author>
<name>Thinh Nguyen</name>
</author>
<published>2022-04-12T01:33:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4377eddfcc07eecce9b04130e8eb47daaafa688a'/>
<id>urn:sha1:4377eddfcc07eecce9b04130e8eb47daaafa688a</id>
<content type='text'>
commit f28ad9069363dec7deb88032b70612755eed9ee6 upstream.

The current driver logic checks against 0 to determine whether the
periodic tx/rx threshold settings are set, but we may get bogus values
from uninitialized variables if no device property is set. Properly
default these variables to 0.

Fixes: 938a5ad1d305 ("usb: dwc3: Check for ESS TX/RX threshold config")
Cc: &lt;stable@vger.kernel.org&gt;
Signed-off-by: Thinh Nguyen &lt;Thinh.Nguyen@synopsys.com&gt;
Link: https://lore.kernel.org/r/cccfce990b11b730b0dae42f9d217dc6fb988c90.1649727139.git.Thinh.Nguyen@synopsys.com
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>usb: dwc3: leave default DMA for PCI devices</title>
<updated>2021-11-17T14:03:51Z</updated>
<author>
<name>Fabio Aiuto</name>
</author>
<published>2021-11-13T14:29:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=47ce45906ca9870cf5267261f155fb7c70307cf0'/>
<id>urn:sha1:47ce45906ca9870cf5267261f155fb7c70307cf0</id>
<content type='text'>
in case of a PCI dwc3 controller, leave the default DMA
mask. Calling of a 64 bit DMA mask breaks the driver on
cherrytrail based tablets like Cyberbook T116.

Fixes: 45d39448b4d0 ("usb: dwc3: support 64 bit DMA in platform driver")
Cc: stable &lt;stable@vger.kernel.org&gt;
Reported-by: Hans De Goede &lt;hdegoede@redhat.com&gt;
Tested-by: Fabio Aiuto &lt;fabioaiuto83@gmail.com&gt;
Tested-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Signed-off-by: Fabio Aiuto &lt;fabioaiuto83@gmail.com&gt;
Link: https://lore.kernel.org/r/20211113142959.27191-1-fabioaiuto83@gmail.com
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>Merge 5.15-rc3 into usb-next</title>
<updated>2021-09-27T14:34:40Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
</author>
<published>2021-09-27T14:34:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ae9a6149884e04b3460bd9d7ffe29c5ec8d223d8'/>
<id>urn:sha1:ae9a6149884e04b3460bd9d7ffe29c5ec8d223d8</id>
<content type='text'>
We need the USB fixes in here as well.

Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>usb: dwc3: core: balance phy init and exit</title>
<updated>2021-09-14T08:34:50Z</updated>
<author>
<name>Li Jun</name>
</author>
<published>2021-09-08T02:28:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8cfac9a6744fcb143cb3e94ce002f09fd17fadbb'/>
<id>urn:sha1:8cfac9a6744fcb143cb3e94ce002f09fd17fadbb</id>
<content type='text'>
After we start to do core soft reset while usb role switch,
the phy init is invoked at every switch to device mode, but
its counter part de-init is missing, this causes the actual
phy init can not be done when we really want to re-init phy
like system resume, because the counter maintained by phy
core is not 0. considering phy init is actually redundant for
role switch, so move out the phy init from core soft reset to
dwc3 core init where is the only place required.

Fixes: f88359e1588b ("usb: dwc3: core: Do core softreset when switch mode")
Cc: &lt;stable@vger.kernel.org&gt;
Tested-by: faqiang.zhu &lt;faqiang.zhu@nxp.com&gt;
Tested-by: John Stultz &lt;john.stultz@linaro.org&gt; #HiKey960
Acked-by: Felipe Balbi &lt;balbi@kernel.org&gt;
Signed-off-by: Li Jun &lt;jun.li@nxp.com&gt;
Link: https://lore.kernel.org/r/1631068099-13559-1-git-send-email-jun.li@nxp.com
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>usb: dwc3: reference clock period configuration</title>
<updated>2021-09-14T08:15:55Z</updated>
<author>
<name>Balaji Prakash J</name>
</author>
<published>2021-08-31T05:57:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7bee31883889018d4bfeae6654a725dd162b5826'/>
<id>urn:sha1:7bee31883889018d4bfeae6654a725dd162b5826</id>
<content type='text'>
Set reference clock period when it differs from dwc3 default hardware
set.

We could calculate clock period based on reference clock frequency. But
this information is not always available. This is the case of PCI bus
attached USB host. For that reason we use a custom property.

Tested (USB2 only) on IPQ6010 SoC based board with 24 MHz reference
clock while hardware default is 19.2 MHz.

[ baruch: rewrite commit message; drop GFLADJ code; remove 'quirk-' from
  property name; mention tested hardware ]

Acked-by: Felipe Balbi &lt;balbi@kernel.org&gt;
Signed-off-by: Balaji Prakash J &lt;bjagadee@codeaurora.org&gt;
Signed-off-by: Baruch Siach &lt;baruch@tkos.co.il&gt;
Nacked-by: Rob Herring &lt;robh@kernel.org&gt;
Link: https://lore.kernel.org/r/9f399bdf1ff752e31ab7497e3d5ce19bbb3ff247.1630389452.git.baruch@tkos.co.il
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>usb: dwc3: Decouple USB 2.0 L1 &amp; L2 events</title>
<updated>2021-08-18T13:31:44Z</updated>
<author>
<name>Jack Pham</name>
</author>
<published>2021-08-12T08:26:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=843714bb37d9a3780160d7b4a4a72b8077a77589'/>
<id>urn:sha1:843714bb37d9a3780160d7b4a4a72b8077a77589</id>
<content type='text'>
On DWC_usb3 revisions 3.00a and newer (including DWC_usb31 and
DWC_usb32) the GUCTL1 register gained the DEV_DECOUPLE_L1L2_EVT
field (bit 31) which when enabled allows the controller in device
mode to treat USB 2.0 L1 LPM &amp; L2 events separately.

After commit d1d90dd27254 ("usb: dwc3: gadget: Enable suspend
events") the controller will now receive events (and therefore
interrupts) for every state change when entering/exiting either
L1 or L2 states.  Since L1 is handled entirely by the hardware
and requires no software intervention, there is no need to even
enable these events and unnecessarily notify the gadget driver.
Enable the aforementioned bit to help reduce the overall interrupt
count for these L1 events that don't need to be handled while
retaining the events for full L2 suspend/wakeup.

Tested-by: Jun Li &lt;jun.li@nxp.com&gt;
Tested-by: Amit Pundir &lt;amit.pundir@linaro.org&gt; # for RB5 (sm8250)
Tested-by: John Stultz &lt;john.stultz@linaro.org&gt; # for HiKey960 &amp; db845c
Reviewed-by: Jun Li &lt;jun.li@nxp.com&gt;
Acked-by: Felipe Balbi &lt;balbi@kernel.org&gt;
Signed-off-by: Jack Pham &lt;jackp@codeaurora.org&gt;
Link: https://lore.kernel.org/r/20210812082635.12924-1-jackp@codeaurora.org
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>usb: dwc3: Resize TX FIFOs to meet EP bursting requirements</title>
<updated>2021-07-12T07:37:26Z</updated>
<author>
<name>Wesley Cheng</name>
</author>
<published>2021-07-10T09:13:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9f607a309fbe95fc1f77acce5af70766a7142537'/>
<id>urn:sha1:9f607a309fbe95fc1f77acce5af70766a7142537</id>
<content type='text'>
Some devices have USB compositions which may require multiple endpoints
that support EP bursting.  HW defined TX FIFO sizes may not always be
sufficient for these compositions.  By utilizing flexible TX FIFO
allocation, this allows for endpoints to request the required FIFO depth to
achieve higher bandwidth.  With some higher bMaxBurst configurations, using
a larger TX FIFO size results in better TX throughput.

By introducing the check_config() callback, the resizing logic can fetch
the maximum number of endpoints used in the USB composition (can contain
multiple configurations), which helps ensure that the resizing logic can
fulfill the configuration(s), or return an error to the gadget layer
otherwise during bind time.

Signed-off-by: Wesley Cheng &lt;wcheng@codeaurora.org&gt;
Link: https://lore.kernel.org/r/1625908395-5498-4-git-send-email-wcheng@codeaurora.org
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>usb: dwc3: Fix debugfs creation flow</title>
<updated>2021-06-21T09:28:18Z</updated>
<author>
<name>Minas Harutyunyan</name>
</author>
<published>2021-06-17T16:55:24Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=84524d1232ecca7cf8678e851b254f05cff4040a'/>
<id>urn:sha1:84524d1232ecca7cf8678e851b254f05cff4040a</id>
<content type='text'>
Creation EP's debugfs called earlier than debugfs folder for dwc3
device created. As result EP's debugfs are created in '/sys/kernel/debug'
instead of '/sys/kernel/debug/usb/dwc3.1.auto'.

Moved dwc3_debugfs_init() function call before calling
dwc3_core_init_mode() to allow create dwc3 debugfs parent before
creating EP's debugfs's.

Fixes: 8d396bb0a5b6 ("usb: dwc3: debugfs: Add and remove endpoint dirs dynamically")
Cc: stable &lt;stable@vger.kernel.org&gt;
Reviewed-by: Jack Pham &lt;jackp@codeaurora.org&gt;
Signed-off-by: Minas Harutyunyan &lt;Minas.Harutyunyan@synopsys.com&gt;
Link: https://lore.kernel.org/r/01fafb5b2d8335e98e6eadbac61fc796bdf3ec1a.1623948457.git.Minas.Harutyunyan@synopsys.com
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>Merge tag 'v5.13-rc6' into usb-next</title>
<updated>2021-06-14T07:18:07Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
</author>
<published>2021-06-14T07:18:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=37fdb7c90f8cc2f41bdf2190ccc44a37bbf1a295'/>
<id>urn:sha1:37fdb7c90f8cc2f41bdf2190ccc44a37bbf1a295</id>
<content type='text'>
We want the usb fixes in here as well, and this resolves some merge
issues with:
	drivers/usb/dwc3/debugfs.c
	drivers/usb/dwc3/gadget.c

Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
</feed>
