Hi Mauro, Am 29.03.2017 um 20:54 schrieb Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxxxxx>: > As we're moving out of DocBook, let's convert the remaining > USB docbooks to ReST. > > The transformation itself on this patch is a no-brainer > conversion using pandoc. right, its a no-brainer ;-) I'am not very happy with this conversions, some examples see below. I recommend to use a more elaborate conversion as starting point, e.g. from my sphkerneldoc project: * https://github.com/return42/sphkerneldoc/tree/master/Documentation/books_migrated/gadget * https://github.com/return42/sphkerneldoc/tree/master/Documentation/books_migrated/writing_musb_glue_layer * https://github.com/return42/sphkerneldoc/tree/master/Documentation/books_migrated/writing_usb_driver Since these DocBooks hasn't been changed in the last month, the linked reST should be up to date. > +Kernel Mode Gadget API > +====================== > + > +Gadget drivers declare themselves through a *struct > +usb\_gadget\_driver*, which is responsible for most parts of enumeration > +for a *struct usb\_gadget*. The response to a set\_configuration usually > +involves enabling one or more of the *struct usb\_ep* objects exposed by > +the gadget, and submitting one or more *struct usb\_request* buffers to quoting of all underlines is not needed. > +!Iinclude/linux/usb/composite.h !Edrivers/usb/gadget/composite.c > +Composite Device Functions > +-------------------------- > + > +At this writing, a few of the current gadget drivers have been converted > +to this framework. Near-term plans include converting all of them, > +except for "gadgetfs". > + > +!Edrivers/usb/gadget/function/f\_acm.c > +!Edrivers/usb/gadget/function/f\_ecm.c > +!Edrivers/usb/gadget/function/f\_subset.c > +!Edrivers/usb/gadget/function/f\_obex.c > +!Edrivers/usb/gadget/function/f\_serial.c > +Peripheral Controller Drivers > +============================= I guess we miss some documentation here. -- Markus -- -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
