Skip to content

usb: Drop requirement for USB unbinding, add tests

Hans de Goede u-boot 2 versions – New

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest4 of 26 patches 0 repliesNew
  2. v13 of 5 patches 0 repliesSuperseded

4 of 26 patches are in this archive. The cover letter announces 26.

Patches in v2 No applies recorded yet

#Subject and filesSizeRepliesApplied
18/26dm: usb: Remove inactive children after a bus scan+0 -04 replies
18/26dm: usb: Remove inactive children after a bus scanarch/arm/Kconfig+1 -00 replies
18/26dm: usb: Remove inactive children after a bus scan+0 -01 reply
18/26dm: usb: Remove inactive children after a bus scan+0 -02 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [U-Boot] [PATCH v2 00/26] usb: Drop requirement for USB unbinding, add tests

Hi Simon,

Quoted 17 lines · Simon Glass

There was quite a bit of discussion about the change that required the unbinding of USB devices for the subsystem to function correctly. E.g.

https://patchwork.ozlabs.org/patch/485637/

The key issue is the usb_get_dev_index() function which is not a good API for driver model. We can drop use of this function once everything is converted to driver model. Then I believe the problems raised by Hans go away. For now we can add a deprecation warning on the function.

It is easy to convert USB keyboards to driver model. This series includes a patch for that.

This series also includes reverts for the three commits which as discussed I would like to drop. U-Boot should be able to run normally and exit without unbinding anything.

Quoted 8 lines

Also included are some tests for the 'usb tree' command. To make this work, console recording is implemented.

Finally, a USB keyboard driver is provided for sandbox, so that this part of the stack can be tested automatically.

Changes in v2:
- Add various patches to support USB keyboards and additional tests

Do you have a git branch with this patch-set somewhere for me to test ?

Regards,

Hans