On Sat, Sep 06, 2025 at 09:04:04AM -0300, Daniel Almeida wrote: > Hi Greg, > > […] > > > > > Sorry for the delay. > > > > But these bindings really are only for a usb interface probe/disconnect > > sequence, right? no real data flow at all? > > > > I recommend looking at the usb-skeleton.c driver, and implementing that > > as your sample driver for rust. That will ensure that you actually have > > the correct apis implemented and the reference count logic working > > properly. You have urb anchors and callbacks and other stuff as well to > > ensure that you get right. That driver pretty much should handle > > everything that you need to do to write a usb driver for any type of > > "real" device. > > > > thanks, > > > > greg k-h > > > I thought that an iterative approach would work here, i.e.: merge this, then > URBs, then more stuff, etc. Ah, that makes sense, I didn't realize you want that here. What USB device do you want to write a rust driver for? Are you going to need bindings to the usb major number, or is it going to talk to some other subsystem instead? Right now, these bindings don't really do anything USB specific at all except allow a driver to bind to a device. thanks, greg k-h
