<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/drivers/usb, branch v2022.04-rc2</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/drivers/usb?h=v2022.04-rc2</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/drivers/usb?h=v2022.04-rc2'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2022-02-11T00:30:43Z</updated>
<entry>
<title>usb: gadget: ci: Avoid null pointer dereference</title>
<updated>2022-02-11T00:30:43Z</updated>
<author>
<name>Marek Vasut</name>
<email>marex@denx.de</email>
</author>
<published>2022-01-28T03:39:09Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=1f54025d70c4c9e6ec8d82d8b69b0d66a7bbbdc1'/>
<id>urn:sha1:1f54025d70c4c9e6ec8d82d8b69b0d66a7bbbdc1</id>
<content type='text'>
The ci_req-&gt;hw_buf can be NULL, test whether it is and if so,
avoid accessing it. Else, the system may crash.

Signed-off-by: Marek Vasut &lt;marex@denx.de&gt;
Cc: Peter Chen &lt;peter.chen@nxp.com&gt;
Cc: Li Jun &lt;jun.li@nxp.com&gt;
Cc: Peng Fan &lt;peng.fan@nxp.com&gt;
</content>
</entry>
<entry>
<title>usb: ehci-mx6: Enable OTG detection on imx8mm and imx8mn</title>
<updated>2022-02-10T23:03:48Z</updated>
<author>
<name>Adam Ford</name>
<email>aford173@gmail.com</email>
</author>
<published>2022-02-03T21:20:11Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=078dfef931523b64c1904517a1a6f04511fe42a2'/>
<id>urn:sha1:078dfef931523b64c1904517a1a6f04511fe42a2</id>
<content type='text'>
The imx8mm and imx8mn appear compatible with imx7d-usb
flags in the OTG driver.  If the dr_mode is defined as
host or peripheral, the device appears to operate correctly,
however the auto host/peripheral detection results in an error.

The solution isn't just adding checks for imx8mm and imx8mn to
the check for imx7, because the USB clock needs to be running
to read from the USBNC_PHY_STATUS_OFFSET register or it will hang.

Marek requested that I not enable the clocks in ehci_usb_of_to_plat,
so I modified that function to return an unknown state if the
device tree does not explicitly state whether it is a host
or a peripheral.

When the driver probes, it looks to see if it's in the unknown
state, and only then will it read the register to auto-detect.

Signed-off-by: Adam Ford &lt;aford173@gmail.com&gt;
Tested-by: Tim Harvey &lt;tharvey@gateworks.com&gt;
</content>
</entry>
<entry>
<title>dfu: handle short frame result of UPLOAD in state_dfu_idle</title>
<updated>2022-01-28T15:21:51Z</updated>
<author>
<name>Patrick Delaunay</name>
<email>patrick.delaunay@foss.st.com</email>
</author>
<published>2021-10-13T15:01:37Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=86b6a38863bebb70a65a53f93a1ffafc4a472169'/>
<id>urn:sha1:86b6a38863bebb70a65a53f93a1ffafc4a472169</id>
<content type='text'>
In DFU v1.1 specification [1] the DFU_UPLOAD (Short Frame)
is handled only in dfuUPLOADIDLE state:

- Figure A.1 Interface state transition diagram

- the state description in chapter A.2

A.2.3 State 2 dfuIDLE
  on Receipt of the DFU_UPLOAD request,and bitCanUpload = 1
  the Next State is dfuUPLOADIDLE

A.2.10 State 9 dfuUPLOAD-IDLE
  When the length of the data transferred by the device in response
  to a DFU_UPLOAD request is less than wLength. (Short frame)
  the Next State is dfuIDLE

In current code, when an UPLOAD is completely performed after the first
request (for example with wLength=200 and data read = 9), the DFU state
stay at dfuUPLOADIDLE until receiving a DFU_UPLOAD or a DFU_ABORT request
even it is unnecessary as the previous DFU_UPLOAD request already reached
the EOF.

This patch proposes to finish the DFU uploading (don't go to dfuUPLOADIDLE)
and completes the control-read operation (go to DFU_STATE_dfuIDLE) when
the first UPLOAD response has a short frame as an end of file (EOF)
indicator even if it is not explicitly allowed in the DFU specification
but this seems logical.

[1] https://www.usb.org/sites/default/files/DFU_1.1.pdf

Signed-off-by: Patrick Delaunay &lt;patrick.delaunay@foss.st.com&gt;
</content>
</entry>
<entry>
<title>Merge tag 'dm-pull-26jan22' of https://source.denx.de/u-boot/custodians/u-boot-dm</title>
<updated>2022-01-27T19:14:47Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2022-01-27T19:14:47Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=761a1786e125ce0e2f472f25f2b841d5f4e2f0cb'/>
<id>urn:sha1:761a1786e125ce0e2f472f25f2b841d5f4e2f0cb</id>
<content type='text'>
acpi refactoring to allow non-x86 use
binman support for bintools (binary tools)
minor tools improvements in preparation for FDT signing
various minor fixes and improvements
</content>
</entry>
<entry>
<title>usb: gadget: Add CDC ACM function</title>
<updated>2022-01-26T22:23:17Z</updated>
<author>
<name>Loic Poulain</name>
<email>loic.poulain@linaro.org</email>
</author>
<published>2021-11-25T17:16:15Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=fc2b399ac03b91339a1cb1bfd4d1a9ca87fe95c6'/>
<id>urn:sha1:fc2b399ac03b91339a1cb1bfd4d1a9ca87fe95c6</id>
<content type='text'>
Add support for CDC ACM using the new UDC and gadget API. This protocol
can be used for serial over USB data transfer and is widely supported
by various OS (GNU/Linux, MS-Windows, OSX...). The usual purpose of
such link is to access device debug console and can be useful for
products not exposing regular UART to the user.

A default stdio device named 'usbacm' is created, and can be used
to redirect console to USB link over CDC ACM:

&gt; setenv stdin usbacm; setenv stdout usbacm

Signed-off-by: Loic Poulain &lt;loic.poulain@linaro.org&gt;
</content>
</entry>
<entry>
<title>usb: ehci: dm: Convert i.MX28 ehci code to driver model</title>
<updated>2022-01-26T22:22:59Z</updated>
<author>
<name>Lukasz Majewski</name>
<email>lukma@denx.de</email>
</author>
<published>2021-12-22T09:55:09Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=07791e8d059037630703857bf5d13d079a3310bb'/>
<id>urn:sha1:07791e8d059037630703857bf5d13d079a3310bb</id>
<content type='text'>
This commit converts i.MX28's EHCI USB host driver to driver model
(DM_USB). It is a straightforward conversion (to reuse as much code
as possible), based on ehci-mx5.c code.

Signed-off-by: Lukasz Majewski &lt;lukma@denx.de&gt;
</content>
</entry>
<entry>
<title>usb: ehci: Move common mxs code to separate functions (ehci_hcd_{stop|start})</title>
<updated>2022-01-26T22:22:59Z</updated>
<author>
<name>Lukasz Majewski</name>
<email>lukma@denx.de</email>
</author>
<published>2021-12-22T09:55:08Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=2d431e33dca2d6b00c00b9c6cfb82bcfca00d3f9'/>
<id>urn:sha1:2d431e33dca2d6b00c00b9c6cfb82bcfca00d3f9</id>
<content type='text'>
Those functions will be re-used when the ehci MXS driver (for imx28)
will be converted to also support CONFIG_DM_USB.

No functional changes introduced - only cosmetic changes (u32 type)
and alignment to pass checkpatch.

Signed-off-by: Lukasz Majewski &lt;lukma@denx.de&gt;
</content>
</entry>
<entry>
<title>usb: ehci: Refactor the ehci_mxs_toggle_clock function to be reused with DM</title>
<updated>2022-01-26T22:22:59Z</updated>
<author>
<name>Lukasz Majewski</name>
<email>lukma@denx.de</email>
</author>
<published>2021-12-22T09:55:07Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=fc313d345a93a6a4edad62683191e11195a75e1e'/>
<id>urn:sha1:fc313d345a93a6a4edad62683191e11195a75e1e</id>
<content type='text'>
This function is going to be reused with the CONFIG_DM_USB enabled in
the imx28 mxs USB ehci driver.

No functional changes introduced.

Signed-off-by: Lukasz Majewski &lt;lukma@denx.de&gt;
</content>
</entry>
<entry>
<title>usb: Modify Kconfig of the USB_EHCI_MXS to use this driver with imx28</title>
<updated>2022-01-26T22:22:59Z</updated>
<author>
<name>Lukasz Majewski</name>
<email>lukma@denx.de</email>
</author>
<published>2021-12-22T09:55:06Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f82feb7f2788035d5ae1463ac8cc8acf0da3d23a'/>
<id>urn:sha1:f82feb7f2788035d5ae1463ac8cc8acf0da3d23a</id>
<content type='text'>
The ehci-mxs driver can be also used with imx28 SoC, not only
imx23.

Signed-off-by: Lukasz Majewski &lt;lukma@denx.de&gt;
</content>
</entry>
<entry>
<title>usb: Use the first available device for ehci_gadget</title>
<updated>2022-01-25T18:47:07Z</updated>
<author>
<name>Sean Anderson</name>
<email>sean.anderson@seco.com</email>
</author>
<published>2021-11-05T16:52:55Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=821ca608d81640f1ed10fc5540eb8df18dfa6679'/>
<id>urn:sha1:821ca608d81640f1ed10fc5540eb8df18dfa6679</id>
<content type='text'>
For whatever reason, usb_setup_ehci_gadget removes and probes USB device
0. However, not all systems have a device 0. Use the first device
instead.

The device probed should probably have something to do with the
controller (as specified by e.g. ums &lt;controller&gt; or fastboot
&lt;controller&gt;). In fact, I find it odd that we probe the USB device in
the first place, because this is just to set up the gadget itself.
Presumably, the controller should be probed by usb_gadget_initialize
somehow.

Signed-off-by: Sean Anderson &lt;sean.anderson@seco.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
